-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[release/7.0] [wasm] Use newer helix images with updated v8 #75725
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
Conversation
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #75271 to release/7.0 /cc @lewing @radekdoulik Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
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.
@karelz I'm hoping this will resolve the flakey RuntimeTest failures, it is correct regardless
|
|
@carlossanlop this is infrastructure only (and only on wasm) |
|
Besides the linked issue above (#74328), the arm64 timeout cancellations have been reported to FR. They are unrelated to this change (affecting many PRs). |
|
Actually, I'm closing this. I already merged the rc2 one and is part of the automatic backport PR: #75713 |
Backport of #75271 to release/7.0
Updates the verision of v8 used to test in CI
/cc @lewing @radekdoulik
Customer Impact
none
Testing
all of it ;)
Risk
Improved CI behavior
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.