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
Feature: Allow to increase WEBDRIVER_TIMEOUT
?
#212
Comments
Note: In case you want to reproduce, this was executed using the latest official docker container ( |
Although I wasn't able to reproduce this error with that particular domain name, I agree this might be "fixed" with setting a longer timeout in the web driver. I will figure out a way to make it configurable - probably with environment variables. |
Thanks! In fact, I also can not reproduce with that domain "now", it seems to be time-dependent — I likely hit a period of high load when running my tests. So having this configurable (environment variables is fine of course) for "flaky servers" seems like a good "solution". |
Currently, the
WEBDRIVER_TIMEOUT
seems hardcoded indnstwist
.This causes flakiness with one of the pages I test, which sometimes has very complex javascript-rich content (sadly), and
dnstwist
errors out with:Would it be possible to add an option to increase this timeout when required?
(I hope this is the correct timeout I am looking at)
The text was updated successfully, but these errors were encountered: