New issue
Advanced search Search tips

Issue 893251 link

Starred by 1 user
Status: Fixed
Owner:
dgarr...@chromium.org
Closed: Oct 10
Cc:
athilenius@chromium.org
la...@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Older "firmwarebranch" builds failing to fetch binary prebuilts during WorkspaceBuildPackages

Project Member Reported by dgarr...@chromium.org, Oct 8 
Some older firmwarebranch builds are failing in BuildPackages because of OAUTH issues.

INFO    : fetching the debug symbols
17:33:09: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.7.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/daisy/paladin-R41-6587.0.0-rc1/packages/Packages
17:33:09: WARNING: GS_ERROR: Your "Oauth 2.0 User Account" credentials are invalid. For more help, see "gsutil help creds", or re-run the gsutil config command (see "gsutil help config").
Failure: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.

17:34:09: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.7.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/daisy/paladin-R41-6587.0.0-rc1/packages/Packages
17:34:09: WARNING: GS_ERROR: Your "Oauth 2.0 User Account" credentials are invalid. For more help, see "gsutil help creds", or re-run the gsutil config command (see "gsutil help config").
Failure: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.


Comment 1 by dgarr...@chromium.org, Oct 8

Cc: la...@chromium.org athilenius@chromium.org
I believe the most resilient way to handle this is to disable binary prebuilts (and perhaps symbol downloading) in "WorkspaceBuildPackages", perhaps gated on the age of the ChromeOS version.

Comment 2 by dgarr...@chromium.org, Oct 8

Summary: Older "firmwarebranch" builds failing to fetch binary prebuilts during WorkspaceBuildPackages (was: Older "firmwarebranch" builds failing to fetch binary prebuilts.)
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 10 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/8d7d6eca5f409d74329fb969a3065bcb491ec521

commit 8d7d6eca5f409d74329fb969a3065bcb491ec521
Author: Don Garrett <dgarrett@google.com>
Date: Wed Oct 10 12:19:46 2018

WorkspaceBuildPackage: Force no prebuilts in older branches.

Create a helper method for testing a version limit against the current
version of the workspace.

Force all builds older than "6589.0.0" to avoid binary prebuilts
because of problems fetching them from branched scripts during
WorkspaceBuildPackages.

This version number will probably need adjusting, but is based on
currently known issues.

BUG= chromium:893251 
TEST=run_tests + tryjob

Change-Id: I37480cfcadc74431b5bd17e267cc4eee781d4a69
Reviewed-on: https://chromium-review.googlesource.com/1268759
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Alec Thilenius <athilenius@google.com>

[modify] https://crrev.com/8d7d6eca5f409d74329fb969a3065bcb491ec521/cbuildbot/stages/workspace_stages.py

Comment 4 by dgarr...@chromium.org, Oct 10 

Believed fixed, verifying in production now.

Adjusting the version number as needed in the future should be straight forward.

Comment 5 by dgarr...@chromium.org, Oct 10

Status: Fixed (was: Started)
►

Sign in to add a comment