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

Issue 610087 link

Starred by 3 users
Status: Verified
Merged: issue 590784
Owner:
dgarr...@chromium.org
Closed: May 2016
Cc:
█ joth@chromium.org
█ davidjames@chromium.org
█ shuqianz@chromium.org
dgarr...@chromium.org
amstan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Chrome prebuilt not available for veyron-rialto release build

Project Member Reported by dgarr...@chromium.org, May 7 2016 
This release builder is failing consistently. The change is probably caused by release builder ungrouping, since this variant probably expected to get it's Chrome prebuilt from a non-variant board in the group.

https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_rialto-release/builds/2

02:24:11: ERROR: Cannot find prebuilts for chromeos-base/chromeos-chrome on veyron_rialto

Comment 1 by davidjames@chromium.org, May 7 2016 

veyron_rialto has sync_chrome=False. This was set because veyron_rialto didn't use Chrome at all when the flag was set. It looks like veyron_rialto does use Chrome now, so suggest just removing the sync_chrome flag (and ask the rialto folks whether their inclusion of Chrome is accidental or not).

Prior to the release builder ungrouping, the sync_chrome=False setting for veyron_rialto had no effect because it was pulling Chrome from the group prebuilts, so it didn't need to sync Chrome to pull prebuilts. So that's why you only are noticing this now.

Comment 2 by rspangler@chromium.org, May 9 2016

Mergedinto: 590784
Status: Duplicate (was: Untriaged)

Comment 3 by davidjames@chromium.org, May 9 2016

Status: Assigned (was: Duplicate)
This builder should be building Chrome from scratch, so it doesn't need a PFQ builder. Based on my reading of  bug 590784  it sounds like the solution is just to delete settings that set 'sync_chrome=False' and 'chrome_sdk=False'.

Comment 4 by dgarr...@chromium.org, May 10 2016

Status: Started (was: Assigned)

Comment 5 by dgarr...@chromium.org, May 10 2016

Cc: dgarr...@chromium.org amstan@chromium.org joth@chromium.org
 Issue 610467  has been merged into this issue.

Comment 6 by dgarr...@chromium.org, May 16 2016

Status: Fixed (was: Started)
HW Tests are failing, but that's a different issue.

Comment 7 by patricia@chromium.org, May 23 2016 

Bulk verified

Comment 8 by patricia@chromium.org, May 23 2016

Status: Verified (was: Fixed)
bulk verified
►

Sign in to add a comment