[release/8.0-staging] Disable WASI CI#128858
Merged
Merged
Conversation
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>
maraf
added
arch-wasm
Contributor
|
Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara |
pavelsavara
approved these changes
Jun 1, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Disables WASI-related CI jobs in the 8.0-staging pipelines to unblock CI after the Ubuntu 26.04 image update (wasi-sdk wasm-ld dependency on libxml2.so.2) caused persistent failures.
Changes:
- Commented out WASI smoke test legs in the main runtime pipeline.
- Commented out WASI smoke tests, simple WASM build tests, and optional WASI library tests in the extra-platforms WASM pipeline.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/pipelines/runtime.yml | Comments out the WASI/WASM smoke and simple build test template invocations to stop scheduling broken WASI legs. |
| eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml | Comments out WASI smoke tests, simple build tests, and optional WASI library tests to fully disable WASI coverage in extra-platforms WASM. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
|
@akoeplinger tell mode please (once it passes build) |
Member
|
disabling experiment wasi CI, infrastructure change only, Servicing-approved. |
Member
|
/ba-g unrelated infrastructure issues |
This was referenced Jun 1, 2026
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #128775
Description
Backport of the WASI CI disable from 9.0-staging to 8.0-staging.
wasm-ldfrom wasi-sdk dynamically linkslibxml2.so.2, renamed tolibxml2.so.16in Ubuntu 26.04, breaking all WASI CI jobs.Contributes to #128772
eng/pipelines/runtime.yml: Comment out WASI smoke tests andsimple-wasm-build-testseng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml: Comment out WASI smoke tests,simple-wasm-build-tests, and optional WASI library testsCustomer 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_wasmreferences 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.