Uh oh!
There was an error while loading. Please reload this page.
[release/9.0][browser] Disable debugger tests on CI (#108178) - #128132
Conversation
(cherry picked from commit 5b9bba7)
akoeplinger
commented
May 13, 2026
Test-only change that we did in main already, marking Servicing-approved. |
Tagging subscribers to this area: @steveisok, @thaystg, @dotnet/dotnet-diag |
There was a problem hiding this comment.
Pull request overview
This PR backports the change to disable (and remove CI wiring for) Mono WASM/browser debugger tests on the release/9.0 branch, addressing CI failures caused by environment/ICU differences (issue #128130).
Changes:
- Removes WASM debugger test submission/build wiring to Helix and eliminates the
wasmdebuggertestsscenario. - Updates browser/wasm Helix targets and validation to drop the
WasmDebuggerTestsscenario. - Removes pipeline templates and path-trigger subsets that previously scheduled debugger test jobs.
Reviewed changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/mono/wasi/Makefile | Removes the Helix submission target for debugger tests. |
| src/mono/browser/Makefile | Removes Helix build/submission targets for debugger tests. |
| src/mono/browser/debugger/Wasm.Debugger.Tests/wasm.helix.targets | Deletes debugger-test-specific Helix work item generation. |
| src/mono/browser/debugger/Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj | Removes the HelixTargetsFile hook. |
| src/libraries/tests.proj | Stops building the debugger test traversal projects and adjusts wasm sample gating. |
| src/libraries/sendtohelix.proj | Removes special-casing for the debugger test scenario and host matrix. |
| src/libraries/sendtohelix-browser.targets | Removes WasmDebuggerTests scenario support and updates scenario validation error text. |
| eng/testing/tests.browser.targets | Removes WasmDebuggerTests scenario support and updates scenario validation error text. |
| eng/pipelines/runtime.yml | Removes scheduling of wasm debugger tests from main runtime pipeline. |
| eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml | Removes wasm debugger jobs from extra-platforms/wasm pipelines. |
| eng/pipelines/common/templates/wasm-debugger-tests.yml | Deletes the dedicated wasm debugger tests pipeline template. |
| eng/pipelines/common/evaluate-default-paths.yml | Removes the wasmdebuggertests path subset used for CI triggering. |
Comments suppressed due to low confidence (1)
eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml:62
- With the debugger test jobs removed from this template, the
debuggerTestsOnlymode now results in an empty pipeline (e.g.,eng/pipelines/runtime-wasm-dbgtests.ymlpassesdebuggerTestsOnly: true, but all job groups are gated onne(parameters.debuggerTestsOnly, true)andexcludeOptionaldefaults to true). Either delete/updateruntime-wasm-dbgtests.ymland remove thedebuggerTestsOnlyparameter/conditions here, or repoint that pipeline to a remaining job group so it still runs something meaningful.
# Disabled for now
#- template: /eng/pipelines/coreclr/perf-wasm-jobs.yml
#parameters:
#runProfile: 'v8'
#onlySanityCheck: true
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
akoeplinger
commented
May 14, 2026
/ba-g unrelated failures on Apple platforms |
190592c
into
dotnet:release/9.0-stagingUh oh!
There was an error while loading. Please reload this page.
Backport of #108178 to release/9.0-staging
Fixes#128130