Skip to content
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

GitHub Action for Cypress doesn't support Cypress 10? #560

Closed
jdborneman-terminus opened this issue Jun 2, 2022 · 3 comments
Closed

GitHub Action for Cypress doesn't support Cypress 10? #560

jdborneman-terminus opened this issue Jun 2, 2022 · 3 comments

Comments

@jdborneman-terminus
Copy link
Contributor

When I try to run my Cypress GH Action, I get the following error:

It looks like this is your first time using Cypress: 10.0.0

[STARTED] Task without title.
[SUCCESS] Task without title.

Opening Cypress...
[3279:0602/130443.877123:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[3460:0602/130446.518349:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[3460:0602/130446.537660:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
You are attempting to use Cypress with an older config file: cypress.json
When you upgraded to Cypress v10.0 the config file was updated and moved to a new location: cypress.config.js

You may need to update any CLI scripts to ensure that they are referring the new version. This would typically look something like:
"cypress open --config-file=cypress.config.js"

My Cypress project works fine locally and I've converted the config file to cypress.config.js (and the old config is gone). I even tried specifying config-file: in my Cypress GH Action with: block parameters to no avail. This is a blocking issue for us.

@jdborneman-terminus
Copy link
Contributor Author

Oh wait. I am pinned at v2. That might be the problem, I'll report back if that was it.

@jdborneman-terminus
Copy link
Contributor Author

Yeah, just saw the release notes for v4. Sorry!

@asartalo
Copy link

Had this happen to me as well. Would help if the migration tool also includes this information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants