BrowserWebDriverContainer: Timeout in containerIsStarted #4469
Comments
Flugtiger
added a commit
to Flugtiger/testcontainers-java
that referenced
this issue
Sep 20, 2021
This fixes testcontainers#4469, getWithTimeout did only apply to the outer lambda, which returned immediately (the inner lambda). Instead wrap getWithTimeout itself inside a lambda.
This was referenced Sep 20, 2021
|
@Flugtiger is it possible that you're encountering this? SeleniumHQ/docker-selenium#1346 #4315 is a workaround which we should be releasing soon - I'm not sure whether this has been fixed on the selenium side as well. |
kiview
pushed a commit
that referenced
this issue
Oct 22, 2021
This fixes #4469, `getWithTimeou`t did only apply to the outer lambda, which returned immediately (the inner lambda). Instead, wrap getWithTimeout itself inside a lambda.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We get a timeout in BrowserWebDriverContainer#containerIsStarted. It seems the fix for #373 is broken. The inner getWithTimout contains a double nested lambda so the timeout is only applied to the outer lambda which returns immediatly. So when "new RemoteWebDriver" gets stuck in the race condition mentioned in #373, retryUntilSuccess throws when it reaches its own timeout in the first try.
The text was updated successfully, but these errors were encountered: