Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not find a Cypress configuration file. We looked but did not find a cypress.json file in this folder.

See original GitHub issue

As of late last week, Cypress tests are failing with this error, from one commit to the next, which was completely unrelated (an .md file). I seem to be getting the same error as @jazanne from this comment.

We’re using:

cypress-io/github-action@v2
Cypress v9.7.0
Yarn Berry v3

I tried @jazanne’s workaround, sadly we’re still getting the same error regardless. We’ve tried upgrading cypress, using cypress-io/github-action@v3, and running it headlessly. In one separate PR I even tried to downgrade to yarn 1.x, which is causing some other errors. The whole JS toolchain seems so brittle. 😒 Is anyone else getting this? Any suggestions?

[STARTED] Task without title.
[SUCCESS] Task without title.
[494:0606/101147.234717:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[494:0606/101147.234801:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[494:0606/101147.234809:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[494:0606/101147.234815:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[655:0606/101148.920788:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[655:0606/101148.926474:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
Could not find a Cypress configuration file.
We looked but did not find a cypress.json file in this folder: /__w/kaoto-ui/kaoto-ui
Error: The process '/usr/local/bin/npx' failed with exit code 1

cc @delawen

Issue Analytics

State:
Created a year ago
Reactions:19
Comments:39 (3 by maintainers)

Top GitHub Comments

9reactions

stychucommented, Jul 19, 2022

Any solutions yet?? Seems like this is a wide issue as of now with cypress v10+.

4reactions

gsoufcommented, Aug 3, 2022

Actually this is working after running the cypress migration. The config file is not a json anymore. It is a JS file now. All I did is running cypress open (from host machine, not from docker) to get cypress ui, and followed the migration from the UI. They migrate the cypress file for us. Then remember to use cypress run with updated flag --config-file to point to the new js file

Top Results From Across the Web

javascript - Could not find any tests to run. We looked but did ...

I have installed Cypress in my project and when I am trying to run the Cypress using npx cypress run , it's giving...

Configuration - Cypress Documentation

This guide is for Cypress 10 and the new JavaScript configuration file format. If you are on an older version of Cypress that...

cypress-io/cypress - Gitter

Could not find a Cypress configuration file, exiting. We looked but did not find a cypress.json file in this folder: /e2e error Command...

Configurations in Cypress and How to Disable Default ...

Now when you expand the configuration, you'll find the default ... Additionally, it guides Cypress where to look for certain files while ...

Cypress — initial setup - Kristijan - Medium

We all know testing is very important for software. ... cypress run --spec folder/test.spec.js. config-file ... cypress run --config-file test/cypress.json.