-
Notifications
You must be signed in to change notification settings - Fork 110
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
Could not connect to the playwright process at port XXXXX #4059
Comments
Hello, this is not issue related playwright evan Robot Framework. You have to disable paralel run on Chromium since it is not supported at your doker. |
Because https://robocon.io/ is coming next week, I am busy doing that related stuff and most likely after that I event I will take some time off from anything related to RF. Therefore it would turn on the community on https://robotframework.org/#community Slack or forum would be my choices. |
Hello, thank you for your comment. I only tested parallel execution experimentally, but all my main tests are run sequentially. So, I am not using parallel execution (nor PabotLib) in my test routine, and the issue still occurs even in sequential execution. |
Thank you! By the way, your nickname looks familiar. I found someone with the same issue in the community, and you mentioned that you had experienced something similar and had found the root cause. I also tried terry.jp suggestion, but it didn’t work for me. |
I'm facing an issue: I can't run my automation using the Browser Library in Docker within a WSL environment. I've tried multiple Dockerfiles and entrypoints, but they all return the same error. I receive a message stating that the Playwright process was not found on port XXXXX, preventing the automation from starting the test.
I found other people on the internet reporting the same error, and they never found a solution. I can't think of anything else to try. I've already tried Launch server, Connect server, and everything I could imagine, but I always get the same error message.
Locally, everything works perfectly. The problem starts when I try to set up my automation in Docker on WSL. I need the automation to run in Docker because I will use it in a pipeline.
I'm coming here because I believe this might be the only place where I can get help. I have a lot of experience with automation in pipelines, and I've never faced a challenge as difficult as this one.
First dockerfile
Second dockerfile:
My custom dockerfile:
The text was updated successfully, but these errors were encountered: