Issue metadata
Sign in to add a comment
|
peach_pit-tot-chrome-pfq-informational failing since April 6 |
||||||||||||||||||||||
Issue descriptionLink to tree: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational?numbuilds=100 First failing build: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/10292 Message: [Test-Logs]: provision: FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos6-row2-rack11-host12: 0) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds, 1) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds Failure appears to be in provision_AutoUpdate. It looks like there may be a powerd crash, unless it is a red herring: [0406/124930:FATAL:powerd_setuid_helper.cc(51)] Check failed: execvp(command, argv) != -1. execv() failed: No such file or directory
,
Apr 12 2018
Hmm. OK. The client logs appear happy. The server logs are as described above: 04/06 12:53:44.904 INFO | server_job:0218| FAIL provision_AutoUpdate provision_AutoUpdate timestamp=1523044424 localtime=Apr 06 12:53:44 Unhandled DevServerException: CrOS auto-update failed for host chromeos6-row2-rack11-host12: 0) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds, 1) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds peach_pit-chrome-pfq is failing with the same symptom (unsurprising). peach_pit-release and peach_pit-paladin are not failing.
,
Apr 12 2018
The chrome logs do not indicate a chrome crash.
,
Apr 13 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by derat@chromium.org
, Apr 12 2018