-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
Upgrades joaquin #224
Upgrades joaquin #224
Conversation
seems to not be running the cypress CI check, so this won't work 😛 . |
Attempt to fix using: cypress-io/github-action#104 (comment)
20ee04a
to
afd61bd
Compare
a24f04c
to
d3ea59a
Compare
Thanks for keeping chipping away at this @jackbravo. I've no idea what's up or even if it's Cypress' fault or if the issue lies elsewhere and Cypress is paying for it. |
@benjie I feel like I need to install a virtual machine with ubuntu 16.04 to test cypress locally. This flow of testing is very slow :-p. And sadly my work machine today is a mac. |
1cab2ea
to
41d3fd8
Compare
41d3fd8
to
fce5867
Compare
I'm running Ubuntu LTS 20.04 and can't reproduce here. I wonder if upgrading |
I know that ubuntu-latest on github-actions means ubuntu 16.04. Maybe we
could try using a newer ubuntu, but cypress is supposed to work on all
versions:
cypress-io/github-action#251
…On Thu, Dec 10, 2020 at 9:59 AM Benjie Gillam ***@***.***> wrote:
I'm running Ubuntu LTS 20.04 and can't reproduce here. I wonder if
upgrading main branch's Cypress only would have the same issues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#224 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADW3QWEODQXUCB7CE5OPDSUDV7BANCNFSM4UP5DBJA>
.
|
@jackbravo did you manage to make any progress with the out of memory? I upgraded our actions to Ubuntu 20.04 and still experiencing the same issue |
@mattvb91 sadly I don't have made any progress, and haven't got the time to investigate other options. |
I also attempted to fix it in #222 but no luck. Can anyone reproduce this outside of GitHub actions? |
I've reproduced it locally! To do so was quite simple in the end:
Turns out we can't even load the browser in this circumstance either; the issue seems to be Next.js related rather than Cypress related! 🎉 |
We get an error like:
Seems to be related to |
Fixed in |
Thanks for your help debugging this everyone! Turned out to be |
Description
Attempts to fix cypress browser crash.
Using fix proposed at: cypress-io/github-action#104 (comment)
Performance impact
Security impact
Checklist
yarn lint:fix
passes.yarn test
passes.RELEASE_NOTES.md
file (if one exists).