-
Notifications
You must be signed in to change notification settings - Fork 88
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
Use node-qunit-puppeteer for CI tests #229
Conversation
I had previously forked the project as it was falling behind, but it's since been more actively maintained so it should be safe to use, and will give us a newer version of Chromium. Should fix #227
Putting back into draft, more complicated it seems. |
|
@@ -5,7 +5,7 @@ on: [push] | |||
jobs: | |||
build: | |||
|
|||
runs-on: ubuntu-latest | |||
runs-on: ubuntu-22.04 |
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.
This is because of a Chromium bug, see puppeteer/puppeteer#12818
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.
I'll subscribe to that bug. Ideally we can re-instate ubuntu-latest
at some point.
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.
Actually, that bug is closed. I'll go hunt for a bug about the override for runs-on
.
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.
I think that was closed because its really a Chromium bug which is here: https://issues.chromium.org/issues/373753919
I had previously forked the project as it was falling behind, but it's since been more actively maintained so it should be safe to use, and will give us a newer version of Chromium.
Should fix #227