kFilesystemVerifierError(47) in autoupdate.EndToEndTest.npo_delta |
|||
Issue descriptionI haven't seen this one before, although there are a couple of auto-filed bugs that match the error name. The main question is whether anything needs to be done, or it is a transient and sufficiently rare error. I am guessing the latter, but we'll see. glimmer-release build 1202 gs://chromeos-autotest-results/105547028-chromeos-test/chromeos4-row7-rack2-host1/debug/autoserv.DEBUG 03/09 00:11:25.099 ERROR| base_utils:0280| [stderr] [0309/191124:INFO:update_engine_client.cc(502)] Waiting for update to complete. 03/09 00:17:40.020 ERROR| base_utils:0280| [stderr] [0309/191739:ERROR:update_engine_client.cc(217)] Update failed, current operatio\ n is UPDATE_STATUS_IDLE, last error code is ErrorCode::kFilesystemVerifierError(47) 03/09 00:17:40.024 DEBUG| autoupdater:0176| exception in update handler: command execution error
,
Mar 13 2017
One explanation for that error is a bad/failing drive. Another is a kernel driver bug, but I'd expect that to show up on all related DUTs. The relevant update_engine code hasn't changed in a very long time, and bugs there would likely affect all duts/board evenly.
,
Apr 3 2017
Looks like another inner update engine failure like kOmahaErrorInHTTPResponse (37). Pass it to @dhaddock since he plan to change the logic of autoupdate_end_to_end test a little bit.
,
Jun 26 2017
CL to change the test is done now so we can probably close this bug if we haven't seen it since April |
|||
►
Sign in to add a comment |
|||
Comment 1 by nxia@chromium.org
, Mar 13 2017Owner: xixuan@chromium.org