Give canary hwtests time till the next run to complete.
Reasons:
1. we see weird (non fatal) delays in running hwtests
2. devices in pool:bvt are just sitting idle between canaries
3. Tpms ask for timed out suite reruns
4. Build sheriffs are confused about how to handle a timeout
5. Most timeouts happen because of suites competing for DUTs
It shouldn't hurt to give the canaries time till the next run.
We should find a better way to monitor 1, one that doesn't involve
failing a build.
TEST=Trybot, unittests.
BUG=chromium:342502, chromium:351381
Change-Id: Ib8ec7cac87b1250eb3c3a28663c0ff2393045903
Previous-Reviewed-on: https://chromium-review.googlesource.com/189232
(cherry picked from commit 8971f9fcc5f12297aaac2f662e35a332651a2eb7)
Reviewed-on: https://chromium-review.googlesource.com/190379
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Dharani Govindan <dharani@chromium.org>
Tested-by: Dharani Govindan <dharani@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
3 files changed
