Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wasm] Switch off HybridGlobalization lane on v8 on CI #101671

Merged
merged 5 commits into from
Apr 30, 2024

Conversation

ilonatommy
Copy link
Member

Fixes #101634.

This PR removes HybridGlobalization tests on v8.

Reasoning:
Maintaining HybridGlobalization tests 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.
HybridGlobalization is 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.

@ilonatommy ilonatommy requested a review from maraf April 29, 2024 07:38
@ilonatommy ilonatommy self-assigned this Apr 29, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-globalization
See info in area-owners.md if you want to be subscribed.

@ilonatommy ilonatommy merged commit 2ad47cd into dotnet:main Apr 30, 2024
90 of 94 checks passed
michaelgsharp pushed a commit to michaelgsharp/runtime that referenced this pull request May 9, 2024
* Stop testing on v8.

* Try to block by scenario,

* Limit scenarios.

This reverts commit 38f64f7.
@ilonatommy
Copy link
Member Author

backport to release/8.0

@ilonatommy
Copy link
Member Author

/azp backport to release/8.0

@ilonatommy
Copy link
Member Author

/backport to release/8.0-staging

Copy link
Contributor

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/9155347363

Copy link
Contributor

@ilonatommy backporting to release/8.0-staging failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Stop testing on v8.
Using index info to reconstruct a base tree...
M	eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml
CONFLICT (content): Merge conflict in eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Stop testing on v8.
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

Copy link
Contributor

@ilonatommy an error occurred while backporting to release/8.0-staging, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

Ruihan-Yin pushed a commit to Ruihan-Yin/runtime that referenced this pull request May 30, 2024
* Stop testing on v8.

* Try to block by scenario,

* Limit scenarios.

This reverts commit 38f64f7.
@github-actions github-actions bot locked and limited conversation to collaborators Jun 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AbbreviatedMonthGenitiveNames_Get_ReturnsExpected_HybridGlobalization failing with string mismatch
3 participants