Uh oh!
There was an error while loading. Please reload this page.
[backport/9.0-staging] Disable WASI CI - #128775
Merged
akoeplinger merged 1 commit intoJun 1, 2026
Merged
Conversation
Co-authored-by: maraf <10020471+maraf@users.noreply.github.com>
Contributor
Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival |
pavelsavara
approved these changes
May 29, 2026
This was referenced May 30, 2026
Open
maraf
marked this pull request as ready for review
June 1, 2026 13:48
akoeplinger
approved these changes
Jun 1, 2026
akoeplinger
commented
Jun 1, 2026
Member
wasi CI was always experimental, infrastructure change only, applying servicing-approved |
Contributor
There was a problem hiding this comment.
Pull request overview
Disables WASI CI jobs on the 9.0-staging branch to unblock rolling builds that are currently failing due to wasi-sdk’s wasm-ld dynamically linking against libxml2.so.2 (no longer present on Ubuntu 26.04 images).
Changes:
- Removes
wasi_wasmfrom the Mono AOT offsets platform matrix and eliminates WASI from CrossAOT Mono job target OS lists/dependencies. - Comments out WASI-related wasm AOT/library/smoke/simple-build test templates in the extra-platforms wasm pipeline.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| eng/pipelines/runtime.yml | Drops WASI from MonoAOTOffsets and CrossAOT_Mono platform/target selections to prevent WASI CI legs from running. |
| eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml | Comments out WASI-specific wasm test job templates for rolling/PR/optional sections. |
💡 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.
akoeplinger
commented
Jun 1, 2026
Member
/ba-g unrelated infrastructure failures |
akoeplinger
enabled auto-merge (squash)
June 1, 2026 13:52
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jun 1, 2026
CopilotAI
added a commit
that referenced
this pull request
Jun 1, 2026
Backport of #128775 wasm-ld from wasi-sdk is dynamically linked against libxml2.so.2, which was renamed to libxml2.so.16 in Ubuntu 26.04. This breaks all WASI CI jobs. Disable them by commenting out the pipeline entries. Contributes to #128772 Co-authored-by: maraf <10020471+maraf@users.noreply.github.com>
akoeplinger pushed a commit
that referenced
this pull request
Jun 1, 2026
main PR #128775 # Description Backport of the WASI CI disable from 9.0-staging to 8.0-staging. `wasm-ld` from wasi-sdk dynamically links `libxml2.so.2`, renamed to `libxml2.so.16` in Ubuntu 26.04, breaking all WASI CI jobs. Contributes to #128772 - **`eng/pipelines/runtime.yml`**: Comment out WASI smoke tests and `simple-wasm-build-tests` - **`eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml`**: Comment out WASI smoke tests, `simple-wasm-build-tests`, and optional WASI library tests # Customer Impact None. WASI CI is already broken; no runtime behavior changes. # Regression Yes — introduced by Ubuntu 26.04 image update (libxml2 soname change). # Testing CI-only change. Verified no uncommented `wasi`/`wasi_wasm` references remain in affected pipeline files. # Risk Low. Disabling CI jobs that are already failing. No production code touched. # Package authoring signed off? N/A — no package changes. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: maraf <10020471+maraf@users.noreply.github.com> Co-authored-by: pavelsavara <pavel.savara@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
main PR #117936
Contributes to #128772
Description
wasm-ldfrom wasi-sdk is dynamically linked againstlibxml2.so.2, which was renamed tolibxml2.so.16in Ubuntu 26.04 (introduced via #126528). This breaks all WASI CI jobs on 9.0-staging. .NET 10 disabled WASI CI in #117936; this ports the CI-only portion of that fix to 9.0.eng/pipelines/runtime.yml:wasi_wasmfrom the MonoAOTOffsets platform listwasifromMonoCrossAOTTargetOSandmonoCrossAOTTargetOSin all three CrossAOT_Mono jobs (linux, windows, macOS)build_wasi_wasm_linux_release_MonoAOTOffsetsfrom theirdependsOnlistseng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml:simple-wasm-build-tests, and optional WASI library testsUnlike #117936, the
FailBuildMSBuild target is not added — only CI pipeline entries are disabled.Customer Impact
WASI CI is currently broken on 9.0-staging, blocking rolling builds. No customer-facing runtime behavior changes.
Regression
Yes — introduced by #126528 (Ubuntu 26.04 image update).
Testing
CI-only change; no code logic modified. Validated that no active
wasi/wasi_wasmreferences remain in the affected pipeline files.Risk
Low. Commenting out CI jobs that are already failing. No production code or build targets touched.
Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.