* [wasm] Pass --web-server-use-cop for threading samples

* CI: Add wasm samples to wasm specific paths list

* CI: trigger library tests builds, when building runtime tests

.. as they depend on it.

* Mono product build jobs only build the runtime, so don't trigger on library changes

* CI: Exclude some eng/pipelines files from triggering pipelines

```yml
    # src/workloads is only used in runtime-official builds
    # where evaluate-paths is not used
    _always_exclude: [
        eng/pipelines/common/evaluate-default-paths.yml
        eng/pipelines/coreclr/*
        eng/pipelines/installer/*
        eng/pipelines/libraries/*
        eng/pipelines/mono/*
        eng/pipelines/runtime*
        src/workloads/*
    ]
```

* wip

* Revert "wip"

This reverts commit 0b08b8d170fbd9168f9bff3470a54f6f40daa783.

* Bump the NoTargets version

* Update src/tests/Common/wasm-test-runner/WasmTestRunner.proj

* Update src/tests/Common/wasm-test-runner/WasmTestRunner.proj

* evaluate-default-paths: add wasm-test-runner to wasm_specific_only subset, so it doesn't trigger non-wasm jobs

* CI: update triggers

- wasm library tests, and build-only should be triggered by wasm changes
  only if there are non-runtime-tests changes, be runtimetest only
  changes already trigger the corresponding job

* CI: don't trigger non-wasm jobs based on wasm pipeline changes

* CI: don't trigger coreclr, or mono jobs based on only wasm-runtime tests changes

* fix

* fix yml .
Co-authored-by: NAnkit Jain <radical@gmail.com>

Backport the workload changes from net7 but and a versionless manifest that represents the netappcurrent so that version bumps will require fewer immediate changes in net9.0

- `Wasm.Build.Tests` installs `wasm-tools`, and `wasm-tools-net7`
- and uses a sdk with both `wasm-tools`, and `wasm-tools-net7` for running, with projects built for `net7.0`
- `net6.0` workload install is attempted, but fails because the `6.0.10` package isn't on public feeds yet

Also,
- Provision chromedriver also, alongwith chrome
- [host] Track change in forwardConsole parameter to forwardConsoleToWS
- Drop UnixFilePermissions.xml, as it is not needed anymore
Co-authored-by: NAnkit Jain <radical@gmail.com>

* [wasm] CI: Trigger wasm jobs on some specific libraries

For example:
- `src/libraries/System.Runtime.InteropServices/*`
    - this includes import generators
- `src/libraries/System.Runtime.InteropServices.JavaScript/*`

These, and the other libraries have browser specific code that should
trigger the wasm tests.

* fix typo

- For PRs with strictly wasm only changes, disables running non-wasm jobs like mobile, or coreclr
- For Wasm.Build.Tests, and debugger only PRs, runs only those jobs
- Run coreclr jobs only if the PR has non-mono/wasm changes

- This will help simplifying the path subsets in
`eng/pipelines/common/evaluate-default-paths.yml`, which would then help
to avoid a lot of unrelated non-wasm builds on PRs

* CI: Tighten the path based triggers for jobs

`subsets`:
- `mono`: exclude all `src/mono/wasm`, since any changes in that will
  trigger the wasm jobs anyway
- `runtimetests`: exclude Wasm.Build.Tests, and Wasm.Debugger.Tests,
  both of which are in `src/tests/BuildWasmApps`, but are *not* related
  to runtime tests.
- `coreclr_jit`: exclude `src/mono/*` completely, unrelated.

Also, exclude `eng/pipelines/common/evaluate-default-paths.yml` from all
the subsets, so changes in that doesn't trigger unncessary builds.

* Address review feedback

- Change base url used for generated code
- Emit message about initial memory size, on native builds
- Don't trigger all the mono jobs based on changes in `src/mono/wasm/debugger`
- Also, truncate all protocol log messages to max line length of 64k. This reduces the proxy log file for tests from `1.0G` to `160M`.
  - truncating can be disabled by setting the environment variable `WASM_DONT_TRUNCATE_LOG_MESSAGES=1`.

Fixes #71727
Fixes #62736

* xplat-setup.yml: Add support for setting `shouldContinueOnError` to

.. `false`.

Currently, xplat-setup.yml passes on `shouldContinueOnError` to the
template with `true` if the parameter was `true`, else it sets the value
based on whether this is for runtime-staging, on a PR.

Which essentially means that runtime-staging defaults to
`shouldContinueOnError: true` for PRs, or we can set it explcitly to
`true` which would affect the rolling builds.

But this does not allow making a runtime-staging job *fail* when *tests
fail*. To support that this change adds a check for a special value
`forceFalse`, which causes the param to explicitly set to `false`. Thus
allowing `runtime-staging` builds to be marked as such.

* [wasm] Add more paths to trigger running tests on CI

* fix comment

- Run all the debugger tests in one helix job, because most of them take a couple of minutes to run. And this would avoid the overhead of individual helix jobs

- Add a no-workloads variant for `Wasm.Build.Tests`, instead of `EMSDK`
  - This replaces the job that used `WasmApp.LocalBuild*` stuff to build
with a `EMSDK` checkout. That case already gets tested with library tests.
   - The `EMSDK` case had been disabled recently due to an Arcade issue
  - Since we have very few tests to run for the noworkloads case, they are
all run in a single helix work item.

Fixes https://github.com/dotnet/runtime/issues/58159
Fixes https://github.com/dotnet/runtime/issues/67887 (by completely removing the `EMSDK` run)

* [wasm] Move the browser provisioning stuff to a new targets file

.. from `DebuggerTestSuite.csproj`. This will allow other projects to
use this too.

* [wasm][debugger] Handle failure to connect to the browser

* [wasm] Improve the browser path lookup

so it can be used outside the debugger tests project too. For example,
with Wasm.Build.Tests+playwright .

* [wasm][debugger] Throw exceptions from tasks correctly

.. using `ExceptionDispatchInfo.Capture` so we get the original stack
trace.

* [wasm][debugger] General improvements in debug proxy

- like logging
- updated API to make it easier to use by other projects, like the
  upcoming wasm-app-host .

* [wasm][debugger] Add support for setting an automatic breakpoint

.. on the first line of the entrypoint method (`Main`). This will be
useful for debugging with the upcoming wasm-app-host, along with the use
of `wait-for-debugger`.

Implemented by @thaystg .

* [wasm][debugger] Add support for wait_for_debugger

If requested, then it will cause invocation of `main` to be delayed till
a debugger is attached.

Implemented by @thaystg

* [wasm] Cleanup in Wasm.Build.Tests

.. in the lead up to wasm-app-host tests.

* [wasm] Update the default paths used to trigger builds on CI

.. to include templates, and provisioning props.

* disable non-wasm builds

* [wasm][debugger] Fix path to artifacts dir

* [wasm] Emit message with bundle path

* [wasm][templates] Make the project use the target dir's name as the

.. project name, instead of always creating `browser.dll`, and
`console.dll`.

* [wasm][debugger] Use a single static instance of HttpClient

.. as recommended by the documentation.

* Revert "disable non-wasm builds"

This reverts commit 7b8b60d58c886e7e66cf2fea910f1feb4d6374f1.

* Address review feedback, and improve the autogenerated bpid

* [wasm] Bump chrome used for testing to 100.0.4896.88

* [wasm] trigger debugger tests when browser version is updated

* [wasm] bump sdk for workload testing to 7.0.100-preview.2.22108.4

* [wasm] dotnet-install.sh logs errors from curl, while trying older urls,

.. don't let that fail the build.

* [wasm] trigger Wasm.Build.Tests when workload-testing.targets changes

* [wasm] trigger Wasm.Build.Tests on CI when eng/Versions.props changes

* [wasm] Update Wasm.Build.Tests to target net7.0 by default

net6 projects don't build with the workload currently. Tests will be
added for that once it is fixed.

* Bump sdk for workload testing to 7.0.100-preview.3.22128.3

* Bump sdk version for workload testing to 7.0.100-preview.3.22151.18

* [wasm] Trigger all wasm jobs, if eng/Version.Details.xml has any changes, so we run a full check on emsdk updates

* fix yml

* Fix merge

* [wasm] Pass isRollingBuild to runtime-extra-platforms-wasm template, to correctly trigger the EAT/AOT builds

* .. and pass isWasmOnlyBuild also

* [wasm] Don't emit warning if runtimeconfig.json cannot be found

Library projects don't have runtimeconfig.json files by default. So,
don't make it a warning. Instead, emit a low importance which might be
useful when debugging.

But library projects can have runtimeconfig.json, like the runtime test
projects. So, don't limit processing that by OutputType.

IOW, if it's found then use it.

* [wasm] Add timestamp to logs

* Download dotnet-install script for installing workloads

Instead of trying to use the script from `.dotnet`, download the script.
`.dotnet` might not exist, for example, when the `global.json` version
matches the system installed one.

* [wasm] WasmAppBuilder: catch UnauthorizedAccessException also

* [wasm] Fix bug in tests

Some helper methods have a `Action<JToken>` parameter. Many tests
pass an async lambda to this, expecting it to get awaited upon.

```csharp
    EvaluateAndCheck (Action<T> locals_fn)
    {
        ...
        locals_fn(); // no await
        ...
    }

    async Task Test()
    {
        EvaluateAndCheck( async (locals) => {
            ...
            CheckNumber(locals, ...);

            await CheckDateTime(locals, ..);
            ...

        } );
    }
```

In the above example, roslyn generates an async-void lambda, so the
compiler never complains about the async lambda being passed.
`EvaluateAndCheck` cannot, and does not await this, but if the lambda happens to
block, then it will return at that point, and the test(calling method) will end,
without ever completing the lambda. And for most tests, the actual
checks are done in that lambda.

This gets hit when `CheckDateTimeValue` tries to fetch properties of a
`DateTime` object. And it started to show up when adding
`ConfigureAwait(false)` to some calls.

* [wasm] Add Wasm.Debugger.Tests wrapper project

This is a proxy/wrapper project for `src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestSuite.csproj`.

- Building the project as part of the regular browser-wasm build
  presents some issues, because of part the tests need use the aspnet
  sdk, and that doesn't work with `browser-wasm`.
- This wrapper project essentially builds the `DebuggerTestSuite`
  project, with some
  properties(`TargetFramework;TargetFrameworks;Configuration;TargetOS;TargetArchitecture`)
  removed so they don't propogate from the parent build.
  - And it packages it up for running the tests on helix

- I did try to convert `DebuggerTestSuite` into a `Wasm.Debugger.Tests`,
  and make it use the library tests infrastructure, but ran into an
  issue
  - it built the project with no `testhost.dll`, so can't use `dotnet
    test`
  - it did get `xunit.console.dll`, but that would fail to run the tests
    because of missing `System.Runtime` (and I'm guessing, other
    assemblies)
    - attempts to publish the project failed
    - So, for now, this is what we have!

* [wasm][tests] Make them friendly to running outside the tree

.. like on helix.

Add new `DEBUGGER_TEST_PATH`, and `CHROME_PATH_FOR_DEBUGGER_TESTS` which
will be set for helix.

And change the appbundle directory name from the misleading `publish/`
to `AppBundle/`.

* [wasm] Tests.cs -> MiscTests.cs

* [wasm] Add support for submitting debugger tests to helix

Also, added `eng/testing/scenarios/WasmDebuggerTestsJobsList.txt` which
is a manually generated list of test classes. This will be changed to be
generated at runtime, in an upcoming PR.

* [wasm] Add debugger tests job for linux, and windows

They follow the same pattern as other wasm jobs:

- build when isFullMatrix
- build in runtime-manual
- Additionally, build when there are changes in:

```
  - src/mono/wasm/debugger/*
  - src/mono/wasm/runtime/*
  - src/mono/mono/*
```

* [wasm] Add new make targets to submit tests to helix

`submit-debugger-tests-helix`
`submit-tests-helix` - submits any library test archives

* Build Wasm.Debugger.Tests from src/libraries/tests.proj

* DebuggerTestSuite: Copy files for the test archive

* [wasm] Fix HarnessTests.BrowserClose

* [wasm] Fix building `ApplyUpdateReferencedAssembly` project on CI

Essentially, disable use of SourceLink which gets enabled by default
when using `-p:ContinuousIntegrationBuild=true`.

Issue: https://github.com/dotnet/runtime/issues/62618

* cleanup

* Wasm.Build.Tests: add missing file

* [wasm] sendtohelixhelp.proj: Error out if there is more than one zip

.. file when running for Wasm.Build.Tests, or Wasm.Debugger.Tests .

* [wasm] Disable DebuggerTests.ArrayTests on helix

Issue: https://github.com/dotnet/runtime/issues/62661

Using `[Trait..` instead of `ActiveIssue` because: https://github.com/dotnet/runtime/issues/62660

* disable non-wasma builds

* sendtohelixhelp.proj: guard against no payload found

* Disable more tests

* add back builds

* [wasm][debugger] Disable failing debugger test

`DebuggerTests.BreakpointTests.BreakpointInAssemblyUsingTypeFromAnotherAssembly_BothDynamicallyLoaded`

Issue: https://github.com/dotnet/runtime/issues/62823

* Try to fix windows command line

* Move debugger-tests for linux to runtime-staging

* Revert "[wasm][debugger] Fix source-link test (#62786)"

.. as it is breaking debugger tests build on windows.

Issue: https://github.com/dotnet/runtime/issues/62892
This reverts commit 81517407.

* Reorganize libs.native

* Fix darwin build

* Fix wasm-win32 build

* Fix pipelines path evaluation

Adds two new jobs to runtime-staging for Windows - AOT, and Wasm.Build.Tests.

AOT - runs with the same conditions as the one in runtime
Wasm.Build.Tests - run for rolling builds, or when a narrow set of paths related to wasm build change
And do this for corresponding job in runtime for linux
Co-authored-by: NAlexander Köplinger <alex.koeplinger@outlook.com>

* fix warnings

* Trigger GCC leg when src/tests is modified

* Add src/native in default paths
Co-authored-by: NAdeel Mujahid <3840695+am11@users.noreply.github.com>

* Apple Silicon coreclr runtime tests

Create SetPathVars_coreclr_AppleSilicon for enabling limited PR runtime testing

Enable coreclr runtime tests on Apple Silicon for isFullMatrix & SetPathVars_coreclr_AppleSilicon.containsChange

* Fix did not find alphanumeric

* Enable OSX.1100.ARM64.Open for PR triggers

This reverts commit 604660b3.

* Remove checkout bundle and job to improve reliability

* comment

* Fix build error

* Rename evaluate paths job to a valid name

* Fix references to evaluate path variables

* Condition evaluate paths dependency on common parameter

* Bring back fetch depth to 20

* PR Feedback

* Add staging pipeline to PRs

* Condition extraSubsets parameter