-
Notifications
You must be signed in to change notification settings - Fork 1.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
SeleniumBase Tests Fail on Gitpod Workspace Requiring Manual Rebuild #20394
Comments
What is the error you get |
Hello @axonasif All my tests with
It's as if a dependency were missing. And when I do |
It sounds like a service is supposed to be up and running on a port? But it isn't running when you initially open the workspace. If I have time, I may take a look at your snapshot but maybe you could figure it out yourself too :) |
Yes, when running As I mentioned in my the description, I don't believe this is a pytest-related issue, as the process works both on my local machine and in the GitLab CI environment using the image example I shared earlier. Additionally, after using the |
Bug description
When launching a Gitpod workspace, SeleniumBase tests do not pass initially. A manual
gp validate
is required to rebuild the image and restart the workspace, after which the tests successfully run.I use the same image on my gitlab ci to run the tests and it works without any changes.
The Dockerfile :
If anyone has insights or suggestions to help diagnose or resolve this issue, I'm open to feedback and recommendations.
Thanks in advance for any help!
Steps to reproduce
task test:pytest
(seleniumbase tests fails)gp validate
(rebuild the image under.gitlab/images/Dockerfile.pyenv
and create new workspace)task test:pytest
and it works.Workspace affected
mkdocs-mkdocsdsfr-jdgyezs0zj0
Expected behavior
After the workspace starts, i can run my
task test:pytest
command and tests works.Example repository
https://gitpod.io#snapshot/c3a0ba9b-fb21-4f03-a8ad-048f7d134d60
Anything else?
No response
The text was updated successfully, but these errors were encountered: