-
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
cypress run -b chrome fails if you attempt to change the baseUrl #2518
Comments
I also saw this and started using |
I'm not able to reproduce this. How are you using the ``npm-lifecycle` module? Since I see that's where this error is being thrown from. |
I have the same issue on windows 10: |
Unfortunately we'll have to close this issue if no reproducible example is provided. Can anyone provide a way to reproduce this? |
I'm experiencing the same problem. Cypress: 3.1.5 On windows 10. |
I also have noticed this issue. Windows 10 I turned on debugging to provide an extract in case it helps. As you can see, the process just fails without any error message.
|
Are you all using Windows 10? May be only happening in there. @flotwig Any ideas on these cli flags and how they should be passed in through Windows? |
Hmm, this definitely looks like a bug, strange that the args appear to be passed in correctly, then they're passed to the server correctly, but it still doesn't work... I wonder if these will act any differently:
|
I can confirm this bug on Win10. Neither switching the quotes around or the arguments as @flotwig suggested works. Setting the baseurl via an environment variable does however. |
I only started seeing the problem with Cypress 3.5.0
For reference, our Cypress tests are here, https://gitlab.com/gitlab-org/gitter/webapp/blob/086ff67a30a838091fec30beedd923a920797cca/test/e2e/e2e-test.js Related issues: Cypress 3.4.1 ✔️
Using
Cypress 3.5.0 ❌
Using
|
@MadLittleMods Can you try again with debug logs enabled, and share those logs here? It will show some more information which we can use to get to the root of the issue.
|
@flotwig For reference, here is the MR where we are updating to Cypress 3.5.0, https://gitlab.com/gitlab-org/gitter/webapp/merge_requests/1631. I just did a workaround using the Cypress 3.5.0 and
|
I'm experiencing the exact same behavior as @MadLittleMods This happened as soon as I upgraded to 3.5 I am running windows 10. |
Released in |
Current behavior:
cypress run fails if you attempt to change the baseUrl from the command line while using the
--browser chrome
optionRunning each of these commands individually work as expected with no errors
> cypress run --browser chrome
> cypress run --config baseUrl=http://localhost:3000
but strangely, combining them both causes the process to immediately exit with an error.
The failure is almost immediate, there is no output from cypress and no tests are run.
It seemed strange, so I tried combining --browser chrome with other options.
This ran as expected with no errors:
> cypress run --browser chrome --config chromeWebSecurity=false
But if you try to set the baseUrl with --env, the same error occurs!
My current workaround is to set the CYPRESS_BASE_URL environment variable manually prior to calling cypress run.
Desired behavior:
> cypress run --browser chrome --config baseUrl=http://localhost:3000
should not fail
Steps to reproduce:
set baseUrl in cypress.json to
localhost:4200
then run
> cypress run --browser chrome --config baseUrl=http://localhost:3000
Versions
Cypress 3.1.0
Windows 10 using git bash
Node 8.11.3
Chrome Version 69.0.3497.100
The text was updated successfully, but these errors were encountered: