Passthrough recovery mode boot (failures)
We can avoid a hard failure here;
checks in place will handle post servod call and system state issues.
BUG=b:400699275
TEST=b8721280673934479521
Change-Id: I1a0ec75b4f81db2d695afe2a3e8568f6033627c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/dev-util/+/6325393
Auto-Submit: Jae Hoon Kim <[email protected]>
Commit-Queue: Derek Beckett <[email protected]>
Tested-by: Jae Hoon Kim <[email protected]>
Reviewed-by: Derek Beckett <[email protected]>
diff --git a/src/go.chromium.org/chromiumos/test/provision/v2/common-utils/cross-over/reboot_from_usb_state.go b/src/go.chromium.org/chromiumos/test/provision/v2/common-utils/cross-over/reboot_from_usb_state.go
index da862bb..0f141f6 100644
--- a/src/go.chromium.org/chromiumos/test/provision/v2/common-utils/cross-over/reboot_from_usb_state.go
+++ b/src/go.chromium.org/chromiumos/test/provision/v2/common-utils/cross-over/reboot_from_usb_state.go
@@ -40,7 +40,8 @@
time.Sleep(waitForPowerOff)
if err := callServodRetry(ctx, log, "power_state", "rec", s.params); err != nil {
setPDRole(ctx, log, "src", s.params)
- return nil, api.InstallResponse_STATUS_PROVISIONING_FAILED, err
+ // A hard failure isn't necessary at this point, as subsequent checks will identify servod call failures and system state problems.
+ log.Printf("Letting passthrough from failed rec mode boot: %s", err)
}
return nil, api.InstallResponse_STATUS_SUCCESS, nil
