To get statistically significant results from smoothness tests on Android I had to increase the page-load count for my perf trybot jobs, what caused them all to fail. I was alerted by prasadv@ that failures were due to the test exceeding a 1h timeout for the test run step and being killed.

Having this timeout is useful but but having it set to 1h is wasteful in cases like this. A full run of these bots takes more than 2.5 hours just for setting them up and if I need to split my testing in many runs I end up having to waste this time all over again.

Could we offer a way to override that timeout when scheduling the perf try job expected to take longer?