-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[release/8.0-rc1] [wasm] Pin chrome version for testing to 115.0.579.x #90644
[release/8.0-rc1] [wasm] Pin chrome version for testing to 115.0.579.x #90644
Conversation
Hybrid globalization tests are breaking with 116.0.5845.0
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #90643 to release/8.0-rc1 /cc @radical Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@carlossanlop test infrastructure fix for the hybrid globalization failures
Tagging subscribers to this area: @directhex Issue DetailsBackport of #90643 to release/8.0-rc1 /cc @radical Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
Backport of #90643 to release/8.0-rc1
/cc @radical
Customer Impact
Tests fail because newer chrome has changed the results when using hybrid globalization
Testing
Risk
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.