Configurable Timeouts?
|
01-14-2015, 05:25 AM
Post: #11
|
|||
|
|||
RE: Configurable Timeouts?
Sorry, my bad - time is for the "minimum duration". There isn't currently a setting that controls per-test time limits. It would probably take about a day to implement on the server and both desktop agents so it could be configured on the server. If you file an issue in github I can take a look at it.
|
|||
01-14-2015, 05:33 AM
Post: #12
|
|||
|
|||
RE: Configurable Timeouts?
Ah makes sense. I don't want to create any more work for you - I'll find a way to work with the current feature set. Thanks Patrick!
|
|||
01-14-2016, 01:07 AM
Post: #13
|
|||
|
|||
RE: Configurable Timeouts?
Hi,
There is setActivityTimeout command available in scripting: https://sites.google.com/a/webpagetest.o...tyTimeout. I wonder if it is possible to change its default value? Per WPT server or per agent. Now it is set to 2000ms and I need more in most cases because in case of very poor performance wptdriver often finishes test run even when there are http requests pending. What is worse such a test has no status to make it possible to know that actually it happened. Artur Artur Sudnik |
|||
01-21-2016, 12:20 AM
Post: #14
|
|||
|
|||
RE: Configurable Timeouts?
Sorry, looking through the code, the only way it gets set right now is with the hard-coded 2 second default or with the script command. Adding a setting is doable, it's just not in the code yet.
|
|||
01-21-2016, 01:09 AM
Post: #15
|
|||
|
|||
RE: Configurable Timeouts?
OK. I can live with that.
Thanks for checking it! Artur Sudnik |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)