-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[BUG] Browsers will not start in GitLab pipeline #6415
Comments
@radekBednarik Is it mandatory to run in headless=false? In case of headless=true - I believe you won't have it. |
@hananmalka hi, well, according to their documenation, their docker images should have xvfb in and should handle headful mode. and secondly, in headless, I am getting a bunch of different errors, I do not want to get into right now |
Could you try using the following Docker image instead? |
Hello @mxschmitt , I tried running this image in headful and headless as well.
I used
|
Hey @radekBednarik, I tried to repro this here: https://gitlab.com/aslushnikov/playwright-repro-for-6415/-/pipelines However, the pipeline worked just fine - browsers all launched and printed their user agents. I didn't use jest-playwright though; should I? If I should, what would be the minimal test that fails for you? |
Hello @aslushnikov is it possible to pm you? The repo which I am trying to run on gitlab is private, since it was POC for for a 3rd party. |
Hi @aslushnikov I do not know, what happened, but it works now ! :D there are still some errors, but browser starts and tests are running. I used this image: mcr.microsoft.com/playwright:v1.10.0-focal
Whoever did whatever, thanks a lot for that :D |
Awesome! Closing this then! |
Context:
jest-playwright config
GitLab pipeline
Describe the bug
When pipeline job will get to the point, where browser are started, I will get following error (using DEBUG=pw:browser*):
If there is something, I should do regarding CI or test runner setup, I am at loss what it is.
Pls help :)
Best
RB
The text was updated successfully, but these errors were encountered: