-
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
Xvfb needs to be installed to be able to run the bitbucket pipeline #14457
Comments
Have you tried using our provided docker images https://github.com/cypress-io/cypress-docker-images? They have all system dependencies installed. Running Cypress requires these outside dependencies be installed before you can run it. https://on.cypress.io/continuous-integration#Advanced-setup Most people find docker images to be helpful since installing directly is difficult, as you mentioned. There's also a blog showing setup for Bitbucket here that may be helpful: https://www.cypress.io/blog/2018/08/30/setting-up-bitbucket-pipelines-with-proper-caching-of-npm-and-cypress/#header |
Now, I solved this issue by using this configuration: package.json:
bitbucket-pipelines.yaml:
This will solve the issue. Thank you @jennifer-shehane you helped me a lot...! |
I am hitting the same issue when trying to run Cypress tests in Jenkins. The tests pass locally but in CI while running in parallel this issue is seen consistently.
Attempt - I tried using xvfb-run -a command as well but got the same error. |
Instead of docker image,.....I tried sending --headless option but even then it failed....ANy other wat to resolve this...It worked ifne when runnign from azure pipelines but running from a azure self hosted Linux vm its giving this issue |
[STARTED] Task without title.
|
Looking into previous tickets, it seems that has to be installed from the NPM libraries which I'm not sure why is asking me to install this since I can't run Sudo under the pipeline.
This is my output:
What we should do to solve this issue?
The text was updated successfully, but these errors were encountered: