New issue
Advanced search Search tips

Issue 747209 link

Starred by 1 user
Status: Duplicate
Merged: issue 746582
Owner:
dhadd...@chromium.org
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

paygen_au: The active image slot did not change after the update. Given that the source and target versions are identical, the DUT likely rebooted into the old image. This probably means that the payload we applied was corrupt.

Project Member Reported by dhadd...@chromium.org, Jul 21 2017

Comment 1 by dhadd...@chromium.org, Jul 21 2017

Mergedinto: 746582
Status: Duplicate (was: Untriaged)
This was also a result of the test failing after the update was complete. The test was testing updating from N->N.

We updated from N->N once and then failed somewhere silly after the update was complete. Then we retried and updated again from N->N but we were writing to the original slot because the first update succeeded even though the test doesn't know that. 

This won't happen when the duplicate bug is fixed
►

Sign in to add a comment