Switch to Chrome Unstable with new Headless mode #20069
Conversation
|
I spent time trying to understand Beta's GL crashes, but I can't reproduce them locally no matter how hard I try. It seems like using swiftshader should mean we don't depend on GPU hardware, but there is still some difference that I can't pin down. Anyhow, though, it is fixed in Dev, so it seems moot. Note that Dev also has some issue with emrun. My best guess there is something to do with the lockfile used to ensure a single instance. I saw errors on that sometimes, and deleting the file helped. emrun kills the chrome process, so that might be causing a bad lockfile situation. |
kripken
changed the title
|
This PR now switches us to Chrome unstable, with new headless, which seems to pass tests (all but emrun, which was disabled before). |
kripken
changed the title
| # current beta. | ||
| wget -O ~/chrome.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb | ||
| # wget -O ~/chrome.deb https://storage.googleapis.com/webassembly/chrome/google-chrome-stable_current_amd64.deb | ||
| wget -O ~/chrome.deb https://dl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb |
There was a problem hiding this comment.
I think "unstable" and "beta" refer to the same thing.
There was a problem hiding this comment.
Why not uncomment line 45 instead then?
There was a problem hiding this comment.
Oops, that's wrong. Unstable==dev.
|
Can you update the PR description? |
After Chrome updated, we can now use unstable/dev with new headless mode and all
tests pass once more.
Previously a Chrome update caused beta to fail with either old or new headless.