Wait not working
See original GitHub issueAs per the manual:
While starting a container is it possible to block […]
- url is an URL which is polled periodically until it returns a HTTP 200 status code. […]
- time is the time in milliseconds to block.
I observe that the wait does not work correctly:
- It marches on happily even for non-200 status codes (such as
HTTP/1.1 405 Method Not Allowed
) - It marches on after the 30 seconds wait, without complaining
I think this is a regression since earlier 0.11 versions.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Explicit wait is not working in Selenium webdriver
Problem is that the Selenium webdriver is still waiting for that element upto 30 secs before giving an error and moving to next...
Read more >How to handle it when explicit wait is not working in Selenium ...
There are multiple ways to handle wait statements in Selenium and since you mention that explicit wait isn't working. Try these: 1. Implicit...
Read more >Wait() not working in functions - Scripting Support - DevForum
I've run into issues that require the use of wait(), but never known how to use it since the script basically just ignores...
Read more >Implicit and Explicit Wait in Selenium WebDriver (Types of ...
Waits help the user to troubleshoot issues while re-directing to different web pages by refreshing the entire web page and re-loading the ...
Read more >Waits - Selenium
To overcome the problem of race conditions between the browser and your WebDriver script, most Selenium clients ship with a wait package.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I fixed that now in that
<time>
is a real timeout if an<url>
or<log>
is present. If only<time>
is specified it simply waits that many millis. 'hope that fits your expectations 😉'will be available in 0.12.0
Verified my use case: