-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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] Use latest chrome for testing #88505
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
Tagging subscribers to this area: @directhex Issue Detailsnull
|
/azp run runtime-wasm |
No commit pushedDate could be found for PR 88505 in repo dotnet/runtime |
879a3de
to
47070e7
Compare
/azp run runtime-wasm |
No commit pushedDate could be found for PR 88505 in repo dotnet/runtime |
@thaystg have you seen this failure before? The trace can be symbolicated, if that helps. |
The message is |
cc @lambdageek |
Does this already fail with an older chrome? |
Looks like it's being hit on |
Opened #88528 |
This was fixed to a specific version (`113.0.5672.63`) because of dotnet#86919 . But trying to use latest again now.
c27582d
to
940f67f
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Failures are unrelated. |
AOT
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
@pavelsavara @maraf any idea about this?
|
It's on this pr. |
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.
Failures are likely caused by #88910
This was fixed to a specific version (
113.0.5672.63
) because of #86919 . But trying to use latest again now.