Could not find a Cypress configuration file. We looked but did not find a cypress.json file in this folder. #564
Comments
|
We got the same issue in a gitlab-ci pipeline. Looks like a driver issue to me: |
|
same issue. anyone looking into this? |
|
Same issue. Using:
Could be related to migrating to v2 of npm lockfile. Had to upgrade chokidar after migration. The run: The file has to be there, since github checkout points to the same folder |
|
Nevermind.. Had to manually update to cypress v10.2.0, since dependabot doesn't run the app. Still a question: why is the error mentioning |
|
@SparrowBrain Thanks for sharing a link to your workflow logs. I had the same issue. In both our cases, you can see in the workflow logs that the
I just changed the workflow to explicitly declare [percy] Running "npx cypress run --headless --config-file cypress.json --browser chrome"
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.ts
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.ts"
https://on.cypress.io/migration-guide |
I have a similar issue, but it doesn't say it can't find the config file, instead : - |
|
Yeah, I'm also getting this when I run it on my local docker. |
|
Any solutions yet?? Seems like this is a wide issue as of now with cypress v10+. |
|
The errors below may not be related to this issue because they also appear in successful runs. Hope this gets fixed soon! libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[491:0626/135959.592121:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[491:0626/135959.594708:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported. |
|
Ya, this sure seems like a widespread issue. I have had to revert to using Cypress 9.5.4 as all the suggestions here have not worked for me. If anybody knows of a working solution, please report here as we really want to Cypress 10.x |
|
+1 - inside docker only happens for open mode Cypress package version: 9.7.0 |
|
Happens to me when upgrading from cypress 9.x to cypress 10.4. It appears to work with cypress 9.7 for me unlike other have mentioned above. |
|
Any workarounds? |
|
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 |
|
any ideas ? im getting this error when i want to use it with docker
|
|
@gsouf any ideas ? with my problem, it seems like you solved it Im using the same version |
|
@javierfuentesm your issue seems to be different to what is described in this ticket. I think you need to put the full path from your app root (from where you invoke in the cypress command) in Or just remove this config because by default cypress will already pick the file at this location (https://docs.cypress.io/guides/core-concepts/writing-and-organizing-tests#Support-file). It just feels weird that the path is not resolved relatively to the config file. Might be an actual issue |
|
@gsouf yes i tried that but is not working , locally it works fine but on docker i get all those errors |
|
@javierfuentesm I got the same error as you did when I tried just That is weird, but overall I noticed many issues with path resolution when I tried to configure the new components testing today. Does that work if you use an absolute path. ie: Have you also tried on an other docker base image? For example could miss something if you are using an alpine image |
|
Is there any updates on this issue? i am also getting error while running in docker.
|
Having the same issue. Any solutions yet? |
|
@iliogr @arnabmondal19 this is not the same error. The error described in this ticket is |
|
@gsouf I know. the error described in the ticket is caused because cypress v10 requires a different config file not cypress.json anymore. however, I am interested in the issue mentioned above regarding dri3 extension not supported :) |
|
@iliogr I don't think that the "dri3 extension" message is an issue. At least for me it's working well in docker and I'm getting the same error message about "dri extension". Is your cypress config file at the root of the your project? If not try to place it at the root of the project to see if it works. There are some ongoing issues with path resolutions when cypress config is not at the root. Also mentioning just in case you missed that.. with cypress 10 default specs files pattern is now using extension Ultimately you can try to set the specPattern manually to an absolute path in your cypress config file: const path = require('path');
const { defineConfig } = require('cypress');
module.exports = defineConfig({
// for e2e testing
e2e: {
specPattern: path.resolve(__dirname, 'path/to/src/**/*.cy.js'),
},
// for component testing
component: {
specPattern: path.resolve(__dirname, 'path/to/src/**/*.cy.js'),
},
})See https://docs.cypress.io/guides/references/configuration#e2e |
|
Having the same issue after upgrading to Cypress version 10. I am running inside of IntelliJ. When I click on a Cypress run configuration to run a test, I get this message:
I have implemented the suggestions noted above... i.e. running with --config-file=cypress.config.ts in my test parameters, specPattern: 'cypress/e2e/**/*.{js,jsx,ts,tsx}' in the cypress.config.ts file, etc. The problem persists. |
|
Would you be able to provide a minimum sample repo with a dockerfile that we can use to reproduce the issue @kodriscollics @iliogr ? |
|
@gsouf and @iliogr ... I figured out the issue (at least for my manifestation of this error). After the upgrade, the value in all of the "Cypress project base:" fields for my Intellij tests were deleted. After I put the proper value back in the fields, the tests run without the error. Here is a look at what I'm talking about:
|
|
any news? |
|
See: https://docs.cypress.io/guides/references/migration-guide#Cypress-Changes "You may use the --config-file command line flag or the configFile module API option to specify a .js or .ts file. JSON config files are no longer supported." It's working for me after changing: /integration/config.json To: /integration/config.js |
|
@drecali kudos, your comment "I just changed the workflow to explicitly declare config-file: cypress.config.ts and it worked." resolved my issue! Thank you. |
|
In my case I found that i had to use
|
|
In my case, I think the problem was I forgot to commit the new files Cypress 10 migration generated. So Cypress ran successfully on my local computer but not on CI. |
|
Hi! Has anyone found a solution to this? We are running cypress in a docker container. Is it necessary to explicitly select the relevant config file? |
|
Look like this problem still exist on |
There are several different problems mixed up in this issue. Which error message are you getting and which version of Cypress are you using? |
version ( on my local OSX )assuming versions are same on CI $ yarn cypress -v
yarn run v1.22.19
warning package.json: No license field
$ /.../node_modules/.bin/cypress -v
Cypress package version: 11.2.0
Cypress binary version: 11.2.0
Electron version: 21.0.0
Bundled Node version: 16.16.0
✨ Done in 0.66s.config// cypress.config.ts
import { defineConfig } from 'cypress'
export default defineConfig({
e2e: {
projectId: 'darxah',
viewportWidth: 1920,
viewportHeight: 1080,
video: true,
baseUrl: 'http://localhost:3000',
chromeWebSecurity: false,
watchForFileChanges: false,
defaultCommandTimeout: 30000,
setupNodeEvents(on, config) {
require('@cypress/code-coverage/task')(on, config)
on('before:browser:launch', (browser: any = {}, launchOptions) => {
// `args` is an array of all the arguments that will
// be passed to browsers when it launches
console.log(launchOptions.args) // print all current args
if (browser.name === 'chrome') {
launchOptions.args.push('--disable-dev-shm-usage')
launchOptions.args.push('--disable-gpu')
}
// whatever you return here becomes the launchOptions
return launchOptions
})
return config
},
},
})problemall tests Pass on my OSX. But fails on CI. with this error [4351:1227/131437.366155:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.tried and same result
github workflow settingname: e2e
on:
pull_request:
jobs:
e2e:
steps:
...
- name: Cypress run
uses: cypress-io/[email protected]
with:
working-directory: e2e
wait-on-timeout: 30 |
I believe that you can ignore the gpu error. I have seen successful tests which also show this error, for example run 6438334587 from this repository's examples. Are you also getting a message like: "Could not find a Cypress configuration file in this folder: /home/runner/work/xxxx" Which runner are you using? If you use If cypress is not in a sub-directory, then you wouldn't need to specify The documentation for working-directory might be confusing because it uses |
|
|
@MikeMcC399 Thank you. Yes. Indeed I am using monorepo. I will try later and let you know the result |
|
|
@MikeMcC399
this is screenshot of github action fail
no other information v5.0.2 gives exact same result on my macbook tests succeed |
|
Thank you for your screen shots and information. You mention only "ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported." This error occurs with Cypress even without using cypress-io/github-action. It does not look like it is preventing your test running on GitHub. If this is the only error you are seeing, then I think you can ignore it. If you want to discuss it more in relation to cypress-io/github-action please open a new issue. This issue is really about the error "Could not find a Cypress configuration file. We looked but did not find a cypress.json file in this folder." |
|
I see. Thank you for explanation. I will try running my test on CI without cypress-io/github-action. ( not sure how to do it ) thank you again |
I'm not sure that you need to do that.
|
|
oh i see. i misunderstood your message. thank you for reproducable example |
|
@matart15 |
|
Are you still experiencing the issue you reported? If not, can this issue be closed now? |
|
No longer having this issue, thanks @MikeMcC399 |
Excellent! Many thanks for your confirmation. |
|
Hi, I have a problem with finding a cypress.config.ts file. Just with The problem is when I try to do it through docker-compose. I tried to copy cypress.config.ts file to /cypress folder. I also tried to investigate Cypress docs, no success.
How to define a path for cypress.config.ts in docker-compose file?! |
|
It does not look like your problem is related to You may find that somebody in the Cypress technical community on Discord can help you solve your problem:
|
|
Thanks @MikeMcC399 |
|
npx cypress open --config-file theNewCypressConfigPath solved by this |
and others
As of late last week, Cypress tests are failing with this error, from one commit to the next, which was completely unrelated (an
.mdfile). I seem to be getting the same error as @jazanne from this comment.We're using:
cypress-io/github-action@v2I 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. :s Is anyone else getting this? Any suggestions?cc @Delawen
The text was updated successfully, but these errors were encountered: