Re-enable the browsertests in Google Chrome on the Windows bot #14509
Labels
Comments
timvandermeij
added a commit
to timvandermeij/pdf.js
that referenced
this issue
Apr 2, 2022
… Windows bot" This reverts commit d476186. The most recent Puppeteer version ships with the most recent Chrome version that should fix the problems we encountered before. Fixes mozilla#14509.
timvandermeij
added a commit
to timvandermeij/pdf.js
that referenced
this issue
Apr 2, 2022
…hrome on the Windows bot (PR 14392 follow-up)" This reverts commit 18c295f. The most recent Puppeteer version ships with the most recent Chrome version that should fix the problems we encountered before. Fixes mozilla#14509.
|
It looks like Puppeteer 13.5.2 did improve things, but not up to the point that we can enable it again. The Windows bot did not fully timeout after 60 minutes anymore, but while completing it still took ~40 minutes and Chrome did eventually timeout in the tests themselves. |
|
Let's just WONTFIX this, since I don't think that it's really worth doubling the runtime of the Windows-bot just to improve testing in Google Chrome; please see PR #16490. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In PR #14392 we disabled the affected configuration, since the Puppeteer update to version
> 13.1.0caused the browsertests to run extremely slowly and then timeout in Google Chrome on the Windows bot.It's possible that this is either a bug in Google Chrome, in Puppeteer, or a combination of them both. In any case, we should figure out why this happens and report the bug(s) to the appropriate project(s). (Unless it turns out to be fixable directly in our test-suite, of course.)
The text was updated successfully, but these errors were encountered: