Issue metadata
Sign in to add a comment
|
cheets_StartAndroid.stress timeout waiting for OOBE
Reported by
jrbarnette@chromium.org,
Jan 8 2018
|
||||||||||||||||||||||||
Issue description
This CQ run failed:
https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17420
The run failed because of cave-paladin:
https://luci-milo.appspot.com/buildbot/chromeos/cave-paladin/2662
This is the test failure message:
cheets_StartAndroid.stress: FAIL: Unhandled TimeoutException: Timed out while waiting 30s for py_utils.WaitFor(lambda: self.oobe_exists, 30).
The test logs are here:
http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/168186783-chromeos-test/
The blamelist for the failed cave-paladin run contains only one CL,
and that CL can't have caused the failure. So, this is a bug in the
test, or in ToT. Passing to the ARC++ constable for triage.
,
Jan 9 2018
I don't know the general policy, but in general I think we actually care about investigating flake bugs. We have so many builders that if we let flake bugs go unfixed then the build is always failing for one flake or another...
,
Jan 9 2018
Regardless of policy, this problem _has_ actually recurred:
https://luci-milo.appspot.com/buildbot/chromeos/edgar-paladin/1887
,
Jan 11 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by linben@chromium.org
, Jan 9 2018