[release/8.0-staging] Switch off HybridGlobalization lane on v8 on CI #102447
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
|
/azp run runtime-wasm |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
Tagging subscribers to 'arch-wasm': @lewing |
maraf
approved these changes
May 20, 2024
carlossanlop
approved these changes
May 20, 2024
carlossanlop
added
Servicing-approved
carlossanlop
merged commit a490202
into
dotnet:release/8.0-staging
111 of 115 checks passed
This was referenced May 21, 2024
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.
Backport of #101671 to release/8.0-staging.
This PR removes
HybridGlobalizationtests on v8.Customer Impact
None, it's CI testing.
Fixes #102348.
Regression
No.
We always tested v8.
Testing, Risk
No testing planned, low risk - customers don't use HG on v8.
Maintaining
HybridGlobalizationtests takes considerable effort - the API response might change with each host version and it does not mean that they are incorrect. As the result, with each version change we have to update expected test results.HybridGlobalizationis primarily targeting browser and node. While updating the tests for browser and node makes sense - to catch any changes that are indeed invalid - updating it for v8 is a not necessary effort.