Issue metadata
Sign in to add a comment
|
Regression: Recovery failed for Jerry device with an unexpected error message while installing 72.0.3623.3/11307.0.0 |
||||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3623.3/11307.0.0 dev-channel Jerry OS: Chrome OS What steps will reproduce the problem? (1)Connect the USB with 72.0.3623.3/11307.0.0 (2)Try to recover the build(Esc+reload+power) and observe. Expected: Should be able to recover the build. Actual: Instead Unexpected Error message is seen This is a Regression issue as build recovery is successful with 72.0.3609.3/11264.0.0 Jerry NOTE: Unable to reproduce the issue on 72.0.3623.3/11307.0.0 dev channel Kip,Reks,Blaze Attaching Recovery Logs.. As the issue already on Reks Issue 906962 got fixed and Reks device is working fine with 72.0.3623.3/11307.0.0 dev, raising another issue.. Bisect Info: Good build:72.0.3609.3/11264.0.0 Bad Build: 72.0.3612.0/11287.0.0 Running command vpd -l shows warning 'VPD partition not formatted. It's fine'
,
Nov 29
cc'ed UI team to check for AU
,
Nov 29
AU successful on Jerry device from M71 dev (11151.4.0) to M72 dev (11307.0.0).
,
Nov 30
Re#3 this will only happen on lab devices without VPD "customization_id" set. So the Jerry you saw may have right ID provisioned and will AU successfully.
,
Dec 1
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/vboot_reference/+/979f8b906cfda7af57a4a526d352216eeafe1746 commit 979f8b906cfda7af57a4a526d352216eeafe1746 Author: Hung-Te Lin <hungte@chromium.org> Date: Sat Dec 01 09:08:50 2018 futility: updater: quirks: Fix firmware names for Veyron family The firmware name for Veyron devices are Google_Veyron_XXX and we have to correct the names in quirks database. BUG= chromium:910085 TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=None Change-Id: I3bf3bbb32fe90ebf370c1bc51c54d0280ddb7e98 Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1354147 Reviewed-by: Youcheng Syu <youcheng@chromium.org> [modify] https://crrev.com/979f8b906cfda7af57a4a526d352216eeafe1746/futility/updater_quirks.c
,
Dec 1
,
Dec 1
Need to merge this to M72.
,
Dec 2
Your change meets the bar and is auto-approved for M72. Please go ahead and merge the CL to branch 3626 manually. Please contact milestone owner if you have questions. Owners: govind@(Android), kariahda@(iOS), djmm@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 3
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/vboot_reference/+/91ef5d83b3e13657a20c9d7fd5e03e4272aee8e6 commit 91ef5d83b3e13657a20c9d7fd5e03e4272aee8e6 Author: Hung-Te Lin <hungte@chromium.org> Date: Mon Dec 03 02:34:01 2018 futility: updater: quirks: Fix firmware names for Veyron family The firmware name for Veyron devices are Google_Veyron_XXX and we have to correct the names in quirks database. BUG= chromium:910085 TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=None Change-Id: I3bf3bbb32fe90ebf370c1bc51c54d0280ddb7e98 Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1354147 Reviewed-by: Youcheng Syu <youcheng@chromium.org> (cherry picked from commit 979f8b906cfda7af57a4a526d352216eeafe1746) Reviewed-on: https://chromium-review.googlesource.com/c/1356692 [modify] https://crrev.com/91ef5d83b3e13657a20c9d7fd5e03e4272aee8e6/futility/updater_quirks.c
,
Dec 3
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hungte@chromium.org
, Nov 29Status: Started (was: Untriaged)