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

Issue 676008 link

Starred by 1 user
Status: Duplicate
Merged: issue 676013
Owner:
█ sbasi@chromium.org
Last visit > 30 days ago
Closed: Dec 2016
Cc:
█ itspeter@chromium.org
akes...@chromium.org
vapier@chromium.org
diand...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

InitSDK Failures in the CQ: chromeos-base/chromeos-fonts failed to emerge

Project Member Reported by sbasi@chromium.org, Dec 20 2016 
Multipler builders displayed this but I see no obvious CL in the CQ to cause it...

https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_spring-paladin/builds/13889/steps/InitSDK/logs/stdio

=== Complete: job chromeos-fonts-0.0.1-r24 (0m2.5s) ===
Failed chromeos-base/chromeos-fonts-0.0.1-r24 (in 0m2.5s). Your build has failed.
Pending 3/23, [Time 07:28:24 | Elapsed 1m38.2s | Load 5.2 2.66 1.4]
Packages failed:
	chromeos-base/chromeos-fonts-0.0.1-r24

Not sure if this is flake or a bug in ToT or a bad CL atm....

Comment 1 by sbasi@chromium.org, Dec 20 2016

Components: Infra>Client>ChromeOS

Comment 2 by diand...@chromium.org, Dec 20 2016

Mergedinto: 676013
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment