New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 831649 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 830321
Owner:
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



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)

Project Member Reported by newcomer@chromium.org, Apr 11 2018

Issue description

FAIL: 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) 
 
Cc: dianwa@chromium.org

Comment 2 by pbe...@chromium.org, Apr 11 2018

Components: OS>Kernel>Graphics
Labels: -Pri-3 Pri-2
Owner: alemate@chromium.org
Status: Assigned (was: Untriaged)
These appear to be identical issues to  crbug.com/830321 .
@alemate, maybe you want to close this as duplicate?

Comment 3 by pbe...@chromium.org, Apr 11 2018

Components: -OS>Kernel>Graphics
removing kernel>graphics component again since on 830321 that was removed as the appropriate component.
Labels: M-67
Cc: kbleicher@chromium.org

Comment 6 by uekawa@chromium.org, Apr 13 2018

Labels: -Pri-2 Pri-0
any update? this is blocking Chrome PFQ.

Comment 7 by uekawa@chromium.org, Apr 13 2018

Mergedinto: 830321
Status: Duplicate (was: Assigned)
after reading the thread, going ahead and merging to  crbug.com/830321 
Status: Assigned (was: Duplicate)
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.

I think this is most likely a duplicate, but we probably need to first figure out the problem with 830321.
> 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.

Comment 11 by josa...@google.com, Apr 13 2018

Labels: ReleaseBlock-Dev OS-Chrome
ok, this one sounds related to  issue 825425  which seems to be blocked by 821237

alemate@ to confirm 

Comment 12 by josa...@google.com, Apr 13 2018

Cc: abodenha@chromium.org derat@chromium.org osh...@chromium.org
 Issue 832189  has been merged into this issue.

Comment 14 by derat@chromium.org, Apr 13 2018

Cc: -derat@chromium.org
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.
Can we tag as fixed per #15, or otherwise reconsider as DEV blocker?
Status: Fixed (was: Assigned)
This is fixed in the  issue 830321 .
Labels: Merge-TBD
[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.
Labels: -Merge-TBD
Owner: cmt...@chromium.org
Status: Duplicate (was: Fixed)
Assigning to cmtice@, sho fixed the 
who fixed the duplicate issue.
Owner: alemate@chromium.org
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.
Cc: llozano@chromium.org

Sign in to add a comment