[wasm] Disable wasm linux library tests which are failing due to infrastructure #114347
Conversation
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
ghost
added
the
needs-area-label
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
eng/pipelines/runtime.yml:819
- Disabling these tests reduces test coverage; please include a comment or reference to a tracking issue explaining the infrastructure issues and the expected timeline for re-enabling the tests.
- - template: /eng/pipelines/common/templates/wasm-library-tests.yml
lewing
added
area-Infrastructure-mono
and removed
needs-area-label
|
Tagging subscribers to this area: @akoeplinger, @matouskozak |
This was referenced Apr 8, 2025
steveisok
approved these changes
Apr 8, 2025
|
/ba-g nativeaot timeouts are unrelated to disabling test |
Sign up for free
to 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.
If there is a better way to do this temporarily, feel free to update the PR
#114348
Failures end up like https://dev.azure.com/dnceng-public/public/_build/results?buildId=1008277&view=logs&jobId=d4e38924-13a0-58bd-9074-6a4810543e7c which build analysis can't do anything useful with.