New issue
Advanced search Search tips

Issue 863629 link

Starred by 2 users
Status: Available
Owner:
la...@chromium.org
Cc:
reinauer@chromium.org
vapier@chromium.org
yueherngl@chromium.org
jclinton@chromium.org
nsanders@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Participants' hotlists:
SIE-infra-request


Sign in to add a comment

firmware-veyron-6588.B branch builders broken

Project Member Reported by nsanders@chromium.org, Jul 13 
Similar gsutil error, I think.

https://uberchromegw.corp.google.com/i/chromeos.branch/builders/veyron_pinky%20firmware%20firmware-veyron-6588.B/builds/313

Error is:

09:47:40: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.7.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/board/veyron_pinky/pfq-R41-6588.312.0-rc1/packages/Packages
09:47:40: 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").

Comment 1 by vapier@chromium.org, Jul 14

Components: Infra>Client>ChromeOS>Build
this shows up on a lot of firmware branches.  they're all using old gsutil versions too.

are you just picking random firmware branches, or are you looking at ones you care about ?  it would help if we could cull uninteresting ones.

Comment 2 by nsanders@chromium.org, Jul 14 

All fw branches need to work for the life of the product. This one has a high device count so it's relatively important.

Comment 3 by vapier@chromium.org, Jul 14

Labels: -Pri-1 Pri-2

Comment 4 by la...@chromium.org, Jul 16

Status: Assigned (was: Untriaged)

Comment 5 by jclinton@chromium.org, Aug 7

Owner: ----
Status: Available (was: Assigned)

Comment 6 by nsanders@chromium.org, Sep 11

Owner: la...@chromium.org
This looks like a straggler from  crbug.com/839949

Comment 7 by la...@chromium.org, Sep 11 

Is this blocking something?

Comment 8 by nsanders@chromium.org, Sep 11 

No, just looked forgotten.

Comment 9 by cindyb@google.com, Oct 12 

Low priority bug, will not be worked soon as team focuses on top priority issues.
►

Sign in to add a comment