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

Issue 792262 link

Starred by 1 user

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Dec 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Sign in to add a comment

Chrome Pre-Flight Exceptions on M64 Branch

Project Member Reported by, Dec 5 2017

Issue description

<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b>
<b>Chrome OS Version: <From about:version: Platform x.x.x.x></b>

Hi, I'm seeing exceptions with the chrome-preflight PFQ for the M64 branch.  I assume this is going to break the PFQ uprev needed for the Wed 12/6 DEV RC target (uprev required).

Builder: samus-chrome-pre-flight-branch release-R64-10176.B

The latest exceptions appear to have failed for different reasons:

#14: Exception steps failed buildpackages
#15: Exception steps failed initialcheckout

Status: Assigned (was: Unconfirmed)
Based on the last failure 

[1;31m15:42:08: ERROR: Failed to generate LKGM Candidate. error: return code: 1; command: git push origin temp_auto_checkin_branch:refs/heads/master
 ! [rejected]                temp_auto_checkin_branch -> master (fetch first)
error: failed to push some refs to ''
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.

This seems like a dup of 790043
Labels: -ReleaseBlock-Dev
Reran; passed.  Removing DEV-Blocker.
Steven, does the LKGM error ring any bells for you?
That output was from a MasterSlaveLKGMSync stage, which (I think) generates the Chrome OS LKGM manifest. I am not particularly familiar with this mechanism.

(I am familiar with the UpdateChromeosLKGM stage run in the PFQ which updates which lkgm manifest Chrome uses for simple Chrome.)

It looks like the builder is succeeding now?

Comment 6 by, Dec 18 2017

Status: Fixed (was: Assigned)
Is this fixed?
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-64; 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-64 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD

Sign in to add a comment