wptdriver multiplying timeout by 4

[craig2005]

For some reason the WPT driver seems to be multiplying the TimeOut by 4. If I put in 300 as the timeout, it says waiting 1200 seconds. If I put in 120, it says waiting 480 seconds.

Is it supposed to do that? I couldn't find any documentation on the wpt driver. I probably just missed it. Sorry if this is an obvious question.

[pmeenan]

Yes. Wptdriver has a failsafe on top of the actual timeout where it will terminate all of the processes and clean up and that's what you are seeing. The code running the test itself will still use the timeout that you have set and try to finish gracefully but if it goes out to lunch for some reason wptdriver will clean it all up.

[craig2005]

(08-14-2014 03:16 AM)pmeenan Wrote:  Yes. Wptdriver has a failsafe on top of the actual timeout where it will terminate all of the processes and clean up and that's what you are seeing. The code running the test itself will still use the timeout that you have set and try to finish gracefully but if it goes out to lunch for some reason wptdriver will clean it all up.

Great, thanks. So is the TimeOut per request or per test?

[pmeenan]

It is per page load. If a test is multiple runs then they are run separately each with the same timeout. If it is a script the timeout is applied to each step.

[craig2005]

(08-14-2014 03:42 AM)pmeenan Wrote:  It is per page load. If a test is multiple runs then they are run separately each with the same timeout. If it is a script the timeout is applied to each step.

Awesome! Thanks again.