[wasm] CI improvements to improve test coverage, and reduce load

[radical]

Reduce load

• Improve detection of darc updates allowing the use of specific dependency updates to control triggering of builds. Example: emsdk update should only trigger wasm builds
  • This is difficult right now because the version gets updated in eng/Versions.props, but since it has lot of other things too, all the builds get triggered.
  • If instead the darc version properties were in a separate file, then we could easily figure out if only a darc dependency was updated
  • If not, then we could piece together this with a script
• webcil task should trigger only wasm builds
• Run chrome, and Firefox debugger tests in a single job (reducing 2 builds)
• Run the AOT smoke test with the EAT job (reducing 1 build) - [wasm] CI: For linux, run AOT smoke tests with the EAT build #82570
• Run the windows AOT test with windows library tests - [wasm] CI: For linux, run AOT smoke tests with the EAT build #82570
• Explore having a few build jobs, and running the tests jobs based on the artifacts - Not doing this, as lesser compute for Build isn't important vs quicker PR runs.
• wasi: add path checks (evaluate-default-paths.yml: Add paths for wasi #81817)
• runtime-wasm-dbg-tests: For a PR, run only the jobs that didn't run on runtime pipeline
• Audit the jobs running on the manual-only pipelines

For better test coverage

• run nodejs tests job OOB
• Add wasi file size perf job
• New runtime-wasm-libtests-aot pipeline that auto-triggers on PRs, as needed, to run all the aot libtests
• Improve CI path-changes-based-triggers to work better, and trigger only necessary builds on PRs (Improve CI path-changes-based-triggers to work better #79127)
• split debugger tests into multiple helix items again with different grouping, as the tests are slower now ([wasm][debugger] Fetching assemblies in the debug proxy is (possibly) slower now #70807)
• Move all the wasm jobs from runtime-staging to runtime ([wasm] Move all the wasm jobs from runtime-staging to runtime #73596)
• Avoid triggering unrelated coreclr, and mono/mobile jobs based on wasm-only changes (CI: Tighten the path based triggers for jobs #74534)
• Make all the unconditional coreclr build, coreclr library tests, dev-innerloop, and dotnet-linker-tests jobs conditional, so they don't get triggered on wasm-only changes. (CI: Reduce the unrelated jobs running on wasm only PRs #74601)
• In runtime-wasm, skip the jobs that ran on any default pipeline ([wasm] Avoid duplicate jobs in runtime-wasm  #74837)
• Split runtime-wasm ([wasm] Split runtime-wasm pipeline into runtime-wasm-libtests, and runtime-wasm-non-libtests #74859)
• Trigger wasm jobs based on some libraries that have browser specific bits ([wasm] CI: Trigger wasm jobs on some specific libraries #75007)

Explore

• Explore identifying library test projects to run based on changes in src/libraries, so we can run them for wasm/AOT, without having to run all the tests
• With the reduced need to run all the wasm tests manually via runtime-wasm, find some way to help the PR author figure out whether a manual run is needed.
• auto-trigger runtime-wasm (with conditions) if extra tests need to be run
  • for example - when we have threading related changes, like the threading samples, then we want to run the threading tests in runtime-wasm, so auto-trigger those

These would apply, and benefit mono/mobile jobs too.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

• Avoid triggering unrelated coreclr, and mono/mobile jobs based on wasm-only changes (CI: Tighten the path based triggers for jobs #74534)
• Make all the unconditional coreclr build, coreclr library tests, dev-innerloop, and dotnet-linker-tests jobs conditional, so they don't get triggered on wasm-only changes
• Explore having a few build jobs, and running the tests jobs based on the artifacts

These would apply, and benefit mono/mobile jobs too.

Author:	radical
Assignees:	radical
Labels:	arch-wasm, area-Infrastructure-mono
Milestone:	-

[lewing]

cc @danmoseley @steveisok

[danmoseley]

thanks for working on this @radical

[radical]

Bumping this for myself, to note that we need to be better about running wasm aot tests on PRs. Some test failures like #85012 slipped through because the AOT tests were not run on runtime, or runtime-extra-platforms pipelines on the PRs.