CI: don't trigger *all* library tests on wasm-only changes #81906
Conversation
This file contains 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
For wasm changes that should trigger wasm library tests, a different subset is used.
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFor wasm changes that should trigger wasm library tests, a different This covers changes in, for example,
|
|
Failures are #74838 and unrelated. |
lewing
approved these changes
Feb 15, 2023
steveisok
approved these changes
Feb 15, 2023
|
Failure is unrelated. |
|
Nice. |
ghost
locked as resolved and limited conversation to collaborators
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.
For wasm changes that should trigger wasm library tests, a different
subset is used.
This covers changes in, for example,
eng/testing/ProvisioningVersions.propswhich is only used for wasm, it will trigger only wasm jobs.