Issue metadata
Sign in to add a comment
|
betty-arc64-paladin VMTest timeout
Reported by
jrbarnette@chromium.org,
Mar 23 2018
|
||||||||||||||||||||||||
Issue description
This CQ slave run failed:
https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-paladin/2118
The VMTest stage in the builder failed twice; this bug concerns
only the _first_ failure:
https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fbetty-arc64-paladin%2F2118%2F%2B%2Frecipes%2Fsteps%2FVMTest__attempt_1_%2F0%2Fstdout
The failure was a timeout of the test run.
This same symptom has happened before (without becoming a CQ failure);
see this recent run:
https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-paladin/2115
,
Mar 26 2018
Probably, we should just bump the timeout to 90 minutes, and see what happens.
,
Mar 26 2018
Dup against existing bug.
,
Mar 26 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jrbarnette@chromium.org
, Mar 23 2018I did a spot check against a recent successful run: https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-paladin/2119 Looking at the logs, it seems like testing there took 50 minutes; the timeout is set to 1 hour. So, it may be that the answer is just to bump the timeout.