-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
error "The "path" argument must be of type string. Received undefined" (docker cypress/indcluded:6.6.0 + gitlab integration on new branch) #15418
Comments
This is throwing an error here: https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/util/settings.js#L61:L61 Is there a reason that the |
Hey @jennifer-shehane. I think path have nothing to do with that. I believe there may be some problem with gitlab-integration? Pipelines: Here you can see external (gitlab-integration): |
@jennifer-shehane hey just a reminder that i provided informations |
Same problem for me |
I'm also getting this issue. Slightly different stack trace:
Cypress 6.5.0, running on Node v14.2.0, yarn 1.22.5. |
Hi, @trevithj. Have you resolved the issue? Or did you find some workaround? |
I'm also getting a similar error, with this stack trace.
I think it has something to do with the .env files. |
Has anyone found a workaround or solution to this problem yet? |
Same problem for me with cypress version v10.11.0.
|
I was getting the same error, but in the end it was caused by a wrong CLI command. I'll describe my scenario in case this helps anyone identify any mistake - if any, probably there's a bug around here. EnvironmentOutput from
Debug informationBy enabling debug with
Notice
ResultI then realized I was adding the |
Well i have the --browser argument but i'm also getting this erorr. In my case i uses matrix parallel execution of jobs and for that reason i need to have the browser as a dynamic value like so: |
I am using gitlab integration, here you can see 2 pipelines ran on the same commit, but different branches, as you can see one fails while other don't: https://gitlab.com/cypresstests/test1/-/commit/27e0ea4dd10bb5c010b52af4d95bb44250c43e20/pipelines
The problem may be, while running pipeline on other branch than master, there's an error:
See more: https://gitlab.com/cypresstests/test1/-/pipelines
The text was updated successfully, but these errors were encountered: