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

Issue 611833 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 611275



Sign in to add a comment

Setup .gitconfig on ChromeOS GCE instances.

Project Member Reported by dgarr...@chromium.org, May 13 2016

Issue description

Even though our GCE instances connect using a service account, we need to have these values in their .gitconfig files. These values are present on ChromeOS physical builders, just not GCE.

We MOSTLY work without these values, but not always.

[user]
	name = chrome-bot
	email = chrome-bot@chromium.org

 
Blocking: 611275
Cc: nxia@chromium.org
Labels: -Pri-3 Pri-1
Upping the priority here, as this is causing the Android PFQ to fail (reliably).

We can keep manually uprevving it, however this means we are always slightly behind where we would be if the automation was working.

What do we need to do to fix this?
Cc: katierh@chromium.org bhthompson@chromium.org
Labels: OS-Chrome
Elliot has a partial CL to resolve this:

https://chromereviews.googleplex.com/424237013/
Looks like this CL landed, are we good now or is there more?
My understanding is that we should be good 30 minutes after that CL lands.
I just forced an Android PFQ build to test the fix.
This seems to be fixed, PFQ is green, thanks!
Status: Fixed (was: Untriaged)
Status: Verified (was: Fixed)
bulk verified
Project Member

Comment 12 by bugdroid1@chromium.org, Jun 1 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/puppet/+/1e10026d2d05e4d85d38cc3e61ca747a59188479

commit 1e10026d2d05e4d85d38cc3e61ca747a59188479
Author: Elliott Friedman <friedman@google.com>
Date: Mon May 16 20:19:46 2016

Sign in to add a comment