Issue metadata
Sign in to add a comment
|
veyron-minnie-chrome-pfq and peach-pit-chrome-pfq are failing due to BaseException in _RunParallelStages <class 'chromite.lib.failures_lib.TestLabFailure'>: HWTest did not complete due to infrastructure issues (code 3) |
||||||||||||||||||||||
Issue descriptionFAIL: Servo initialize timed out., Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row9-rack9-host2: 0) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds, 1) RootfsUpdateError: After update and reboot, Chrome failed to reach login screen within 180 seconds ... BaseException in _RunParallelStages <class 'chromite.lib.failures_lib.TestLabFailure'>: HWTest did not complete due to infrastructure issues (code 3)
,
Apr 11 2018
These appear to be identical issues to crbug.com/830321 . @alemate, maybe you want to close this as duplicate?
,
Apr 11 2018
removing kernel>graphics component again since on 830321 that was removed as the appropriate component.
,
Apr 12 2018
,
Apr 12 2018
,
Apr 13 2018
any update? this is blocking Chrome PFQ.
,
Apr 13 2018
after reading the thread, going ahead and merging to crbug.com/830321
,
Apr 13 2018
This is a new bug, unrelated to bug 830321 . The symptom is that Chrome crashes at boot, and the cause is a change in Chrome sources introduced on or after the PFQ runs at 20:51 on 4/8.
,
Apr 13 2018
I think this is most likely a duplicate, but we probably need to first figure out the problem with 830321.
,
Apr 13 2018
> I think this is most likely a duplicate, but we probably need to first figure out the problem with 830321. This is _emphatically_ not a duplicate of bug 830321 . It's a new bug. * This bug fails only the the PFQ, not the canaries. The other bug fails in the canaries, not the PFQ. * This bug started no sooner than 4/8; the other bug started on 3/29. * This bug occurs only on two ARM platforms; the other bug is seen only on two Intel platforms.
,
Apr 13 2018
ok, this one sounds related to issue 825425 which seems to be blocked by 821237 alemate@ to confirm
,
Apr 13 2018
Issue 832189 has been merged into this issue.
,
Apr 13 2018
FWIW, peach_pit-tot-chrome-pfq-informational went green today: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/10384
,
Apr 13 2018
,
Apr 14 2018
I could not reproduce this. My local Chrome OS image build succeeded. The image from the builder is definitely broken, but all the Chrome builds that I tried to deploy on it, succeeded.
,
Apr 16 2018
Can we tag as fixed per #15, or otherwise reconsider as DEV blocker?
,
Apr 17 2018
,
Apr 17 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.
,
May 2 2018
Assigning to cmtice@, sho fixed the
,
May 2 2018
who fixed the duplicate issue.
,
May 3 2018
re-assigning to alemate@. This issue has nothing to do with me. It also cannot be related to issue 830321 , which was related to CFI, which was ONLY enabled on terra & caroline; never on veyron_minnie or peach_pit.
,
May 3 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by newcomer@chromium.org
, Apr 11 2018