We should probably configure the test runners to have a slightly lower timeout than the swarming timeout so they can detect when they're going to fail and exit with an appropriate status.

Swarming timeouts aren't an issue about swarming so moving this to Infra>Client>Chrome. Ideally test runners will have shorter timeouts than what the swarming task timeout is set to so callers know if the test runner hung or just took long. If it hung we can justifiably assign the issue to the test runner owner. If the tests just took long it could be a regression and a sheriff or CL author should be looking at it.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Has been a year. No point in keeping this bug around.