ChromeOS commit bot lies about timeout |
|
Issue descriptionChrome Version: 67.0.3396.79 (Official Build) (64-bit) OS: gLinux What steps will reproduce the problem? See https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1100543#message-3006fd0af0d013b26860f2da73e50391360fc1bb The commit bot says the betty pre-cq trybot timed out after 240 minutes, when in reality an individual stage of the build timed out after 90 minutes. A related issue is that I can't see individual test results. Also, in the same CL, it seems that some of the runs timeout instantly. What is the expected result? An individual test failure due to timeout.
,
Jun 19 2018
Is it possible it was posted before the swarming job finished? It should have known about the timeout at the gerrit timestamp time. I can't see why it would wait the whole 4 hours.
,
Jun 19 2018
I don't know, it makes it extra confusing that Gerrit is in UTC. I'm still not sure what you mean about waiting? The HWTest (attempt 2) didn't finish in time, so the swarming bot killed the entire run assuming it would never come back.
,
Jun 20 2018
I see gerrit in PDT (UTC - 7), not in UTC. The times in goldeneye pointed to by the links don't really make sense though... |
|
►
Sign in to add a comment |
|
Comment 1 by athilenius@chromium.org
, Jun 19 2018