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

Issue 597528 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

rambi-release build_packages taking 7 hours

Project Member Reported by kevcheng@chromium.org, Mar 24 2016

Issue description

rambi-release normally takes about 2 hours for build_packages (at least on build #648)
https://uberchromegw.corp.google.com/i/chromeos/builders/rambi-release/builds/648/steps/BuildPackages%20%5Bafdo_use%5D

but since then, the time has exploded up to around the 7 hour mark
https://uberchromegw.corp.google.com/i/chromeos/builders/rambi-release/builds/671/steps/BuildPackages%20%5Bafdo_use%5D

This causes the unittest step to timeout and the build doesn't complete.
 
This started on builds after 3/15
Cc: dgreid@chromium.org
adding current tree sheriff
Cc: lhchavez@chromium.org
And build 674 is slow again :/
Status: WontFix (was: Untriaged)
Build 674 was slow, but not 7h slow. Builds 675 and 676 are fast again. Didn't find anything odd in the logs of the slow builds(like some rogue process taking up CPU cycles).

Chalking this up to a transient state that has resolved itself.

Comment 7 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Sign in to add a comment