Adjust timeout limit of performance_test_suite on builders with many shards |
|
Issue descriptionRun https://ci.chromium.org/buildbot/chromium.perf/linux-perf/319 took a long time because one bot died after we trigger test (https://chrome-swarming.appspot.com/task?id=3e631b4d49a7cf10&refresh=10&show_raw=1) However, that list to the whole build stalled until timed out (which is 10 hours). There are two things we can do to improve: 1) Upon finding the situation is "1 bots could possibly run this task (0 busy, 1 dead, 0 quarantined, 0 maintenance)", swarming task should end early 2) The max timeout limit should be around 2-3 hours, not 10hours. |
|
►
Sign in to add a comment |
|