-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Browser container fails to start time after time #257
Comments
@pavelpp sorry for taking an age to respond on this one. The logs don't seem to indicate why the container was taking too long to start - did you get anywhere with this? |
@pavelpp any news? :) |
still failing time after time. Even when running the same test with IDE. I usually just abort test and restart, otherwise I'll have to wait 2 minutes until container is restarted. |
I hope this will be fixed by #381 - sorry it took a while to reproduce and figure out why it was happening. It looks like it's essentially happening if With #381 as-is, I've set the timeout for individual WDYT about these limits? |
Closing due to inactivity. |
I see this happening time after time (see below). It slows down tests as tc is retrying to start container until success. I'm trying to understand where the problem is. Should it be reported under docker selenium or here?
The text was updated successfully, but these errors were encountered: