search

FuckTheWorld / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

Tweak timeouts in ChromeDriver #1105

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Timeouts in ChromeDriver need to be tweaked so that bad tests don't spend too 
long waiting for errors to be reported. One example is below:

[9.255][INFO]: Waiting for pending navigations...
[9.255][INFO]: Done waiting for pending navigations
[9.473][INFO]: Waiting for pending navigations...
[309.473][SEVERE]: Timed out receiving message from renderer: 299.444
[309.473][INFO]: Timed out. Stopping navigation...
[858.770][SEVERE]: Unable to receive message from renderer
[858.770][INFO]: Done waiting for pending navigations
[858.770][INFO]: RESPONSE Navigate

We know the renderer has already died at 309s. The navigation tracker really 
should stop waiting for pending navigations at 309s, rather than 858s. That'll 
mean we get down from a 13 minute wait to 5 minutes.

Consider also adding a command-line switch to control the timeout.

Original issue reported on code.google.com by samu...@chromium.org on 22 May 2015 at 5:27

GoogleCodeExporter commented 9 years ago 
Issue 1108 has been merged into this issue.

Original comment by gmanikp...@chromium.org on 26 May 2015 at 6:35

GoogleCodeExporter commented 9 years ago 
Perhaps we should also look at alternatives to timeouts for detecting renderer 
crashes?

Original comment by jbudor...@chromium.org on 27 May 2015 at 6:13