asuka release: autoupdate_EndToEndTest.paygen_au_canary_full: reboot command failed |
||||
Issue descriptionhttps://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/113408814-chromeos-test/chromeos6-row1-rack22-host19/ ======== * Command: /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_6pUUg1ssh- master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos6-row1-rack22-host19 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::run_op|reboot|run_background] -> ssh_run(( sleep 1; reboot & sleep 10; reboot -f ) </dev/null >/dev/null 2>&1 & echo -n \\\$!)\";fi; ( sleep 1; reboot & sleep 10; reboot -f ) </dev/null >/dev/null 2>&1 & echo -n \$!" Exit status: 255 Duration: 37.9510149956 =========
,
Apr 20 2017
One theory is that the reboot is so fast that the ssh has no chance to be finished correctly. Eventually, it's timeouted. But I cannot verify the theory the issue locally. Maybe related to network condition.
,
Apr 20 2017
[paygen_au_canary] autoupdate_EndToEndTest.paygen_au_canary_full Failure on chell-release/R60-9478.0.0 This report is automatically generated to track the following Failure: Test: autoupdate_EndToEndTest.paygen_au_canary_full. Suite: paygen_au_canary. Chrome Version: 59.0.3070.0. Build: chell-release/R60-9478.0.0. Reason: reboot command failed. build artifacts: https://storage.cloud.google.com/?arg=chromeos-image-archive/chell-release/R60-9478.0.0. results log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/113441630-chromeos-test/chromeos4-row12-rack9-host15/debug/. status log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/113441630-chromeos-test/chromeos4-row12-rack9-host15/status.log. buildbot stages: NA. job link: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=113441630. You may want to check the test history on wmatrix: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=autoupdate_EndToEndTest.paygen_au_canary_full You may also want to check the test retry dashboard in case this is a flakey test: https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=autoupdate_EndToEndTest.paygen_au_canary_full ANCHOR TestFailure{paygen_au_canary,autoupdate_EndToEndTest.paygen_au_canary_full,reboot command failed}
,
Apr 21 2017
Another similar issue: https://bugs.chromium.org/p/chromium/issues/detail?id=598345
,
May 1 2017
Can we close this? I no longer see the error on asuka-release.
,
May 1 2017
We have a couple of bugs open for this problem. In all cases I've seen, this contributes to flake, but it's not frequent enough to deserve a P0. Maybe this is now reproducing every time?
,
May 5 2017
Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable? If a fix is in active development, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 19 2017
Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable? If a fix is in active development, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 15 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by owenlin@chromium.org
, Apr 20 2017