-
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
Jenkins Pipeline Error "Cannot create BrowserWindow before app is ready" #918
Comments
Interesting, how can we recreate this failure? Is there a small example public repository that shows this behavior? |
My tests started running randomly but then this issue came up again. After looking into it more, I noticed the tests started working after changing the way I was defining env vars in my Jenkinsile. I made dynamic env vars with bash scripts grabbing the current branch name and date for naming reports that I am autogenerating. When ran a simple cypress run with no extra arguments, my tests started running again. With Jenkin's crazy idiosynchrasies I think I will find another way to get this information or just have simpler report titles... this caused too many headaches for me. |
Just found out that I have the same problem. I will try to reproduce it in a public repo. possibly related: has somebody found a workaround? |
Funny enough I got this error again yesterday evening when we reset our build server. This time I notice this in the logs before the ‘BrowserWindow’ error came up.
|
I found this: https://issues.jenkins-ci.org/browse/JENKINS-23736 Last time I debugged this issue, I physically logged in on the machine and ran the cypress tests myself during debugging, and never logged off. I think this may be our answer, going to try it out when I get into work. |
No luck with having the account logged in. I was able to run cypress manually but the automated cypress command doesn't work. |
Seems like this error is specific to MacOS, ran on our Jenkins server running on Ubuntu and everything is working fine. Possible fix could be using Cypress's docker image? https://github.com/cypress-io/cypress-docker-images |
Same issue on Mac High Sierra v10.13.6 |
I've Mojave 10.14.2 (18C54) and I'm still getting the same problem. I have Jenkins locally installed on my mac and I want to run the sample tests
|
Can you attempt to follow these directions? May be related to Jenkins permissions issues https://stackoverflow.com/a/21028195/5878476 |
Probably not related to permission, I did whatever this thread suggesting me but got no lucky. |
I'm attempting to run some cypress tests on SemaphoreCI within their OSX environment and am encountering this issue as well. OSX : 10.14.5 When running "cypress run", the following error shows:
After searching around, I haven't found a way to get this to work. So I resorted to installing Chrome, ie After installing Chrome into /Applications, I then run
So it appears that one is actually able to run the test, but it's just not able to run the test using electron chromium browser, but it's able to run it using the external Chrome app. This now appears to be more of a Cypress issue more so than SemaphoreCI's OSX. It also appears that the errors are different between running under electron vs chrome. |
Could be old Electron version issue, I wonder if Electron upgrade in #4355 or #4354 fixes this. I will add Mac build to the Semaphore v2 CI project in https://github.com/cypress-io/cypress-example-kitchensink to see if we can recreate the problem - and to confirm that Electron upgrade fixes it when it is released |
I have set up Mac CI build cypress-io/cypress-example-kitchensink#269, it is showing the problem, let's recheck after upgrading Electron version |
Since this issue hasn't had activity in a while, we'll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we'd be happy to reopen. |
I am running into this now on a Mac OS X Catalina 10.15.6 machine with Cypress 6.3.0 where previously the Cypress tests had been running fine for months. Here's the output:
|
And now strangely, after not working several times in a row, I just ran again and it worked. Two possibilities come to mind:
|
Is this a Feature or Bug?
Bug
Current behavior:
Running Cypress on a Jenkins build pipeline returns the following error:
Desired behavior:
Run cypress as part of the testing stage in Jenkins pipeline.
The text was updated successfully, but these errors were encountered: