-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[Taskcluster] pin Chrome Dev to 91.0.4449.6 #28238
Conversation
d850859
to
81bd31a
Compare
Before I merge this I'm going to combine it with a recently blocked PR and see if it works when running some affected tests. |
I pushed a trigger run of this (at 81bd31a) to |
@stephenmcgruer do you think we should wait for a full run to finish, or just see that it's in progress? #28239 has finished wpt-chrome-dev-results which failed on #28237 so I'd be confident enough merging this now. |
I'll just wait for sink-task to go green before merging this. |
This reverts #28238. Update expactations for websockets over h2, which now works.
…91.0.4449.6", a=testonly Automatic update from web-platform-tests Revert "[Taskcluster] pin Chrome Dev to 91.0.4449.6" (#28464) This reverts web-platform-tests/wpt#28238. Update expactations for websockets over h2, which now works. -- wpt-commits: e2fe814ee728461bf4f14f5b8b705c565c48bd1c wpt-pr: 28464
This is a temporary measure while the cause of the crash is being
investigated. This follows a similar approach taken before:
#19360
Mitigation (not fix) for #28209.