-
Notifications
You must be signed in to change notification settings - Fork 322
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
New chrome:92 image flakiness with selenoid 1.10.4 #1124
Comments
Selenoid logs:
I have done this using selenoid 1.10.4, chrome:92 image provided by aerokube and requested the container using selenoid-ui. |
When having a successful container start after several crashes/timeouts with retry count 10, in the browser container logs I see this:
I hope it is somewhat useful for debugging the issue. |
More info: |
Let's try to add |
So from yesterday I can confirm that the container manages to start if we start a headless chrome. |
I have the same issue. Where I have to put "Host: localhost" ? |
Please check whether it works with |
Sorry, still seems to be unstable, tried with the new |
Then this is not related to |
Is it any updates? Have the same issue |
@OHaimanov the only solution right now is to set |
For me helped to use chrome 91.0 instead of 92.0. |
Of course that helps, but that ruins the point of using the latest and greatest chrome and testing against it. |
Hi is this issue resolved, i am still seeing issues when i use chrome 92. I keep getting |
@edurb did you try to add |
same here, unable to upgrade to selenium.common.exceptions.WebDriverException: Message: New session attempts retry count exceeded |
i had to go back to older version of browser because of this 92 issues. but again i am seeing seeing now with #1129 |
@edurb we are going to rebuild Chrome 92.0 image with disable-gpu flag soon. |
Rebuilt Chrome 92.0 image with |
Works for me with the new Also works for edge 92, 93. |
seems better @vania-pooh |
Closing. |
Hi!
Since the friday release of selenoid 1.10.4 and chrome 92.0 browser image we experience some flakyness when executing tests.
The chrome 92.0 image does not work with selenoid 1.10.3 at all, resulting in a
WebDriverError: Host header or origin header is specified and is not whitelisted or localhost.
error.When running selenoid 1.10.4 with the chrome 92.0 image, we see tests fail randomly with
WebDriverError: New session attempts retry count exceeded
. This seems like the new image might not work as expected.We have added a retry count to affected tests, but that does not fix fully the issue, sometimes it still can happen.
Any ideas of how to correct this issue? Maybe the image was not built properly and a rebuild is required?
The text was updated successfully, but these errors were encountered: