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

Issue 678301 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

BuildPackages stuck building autotest-tests-cheets for kefka-release

Project Member Reported by semenzato@chromium.org, Jan 4 2017

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/kefka-release/builds/729/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio

Snippet:

Pending 3/660, Building 1/1, [Time 01:49:21 | Elapsed 416m17.5s | Load 0.0 0.01 0.05]
Still building autotest-tests-cheets-0.0.1-r308 (275m37.2s). Logs in /tmp/autotest-tests-cheets-0.0.1-r308-wMfd89

@@@STEP_FAILURE@@@
01:50:42: ERROR: Timeout occurred- waited 27177 seconds, failing. Timeout reason: This build has reached the timeout deadline set by the master. Either this stage or a previous one took too long (see stage timing historical summary in ReportStage) or the build failed to start on time.

It would be interesting to see what it got stuck on.  There is a path to a log file, but I cannot find the builder name.  Would it be possible to add it to this log?

 

Comment 1 by nxia@chromium.org, Jan 4 2017

You can find the BuildSlave at the build page:
https://uberchromegw.corp.google.com/i/chromeos/builders/kefka-release/builds/729/

BuildSlave:

cros-beefy38-c2

Comment 2 by nxia@chromium.org, Jan 4 2017

It's a global deadline set by the master, it has no information about what took too long. In this case, BuildPackages took 7 hours, which is way too long. people need to investigate. 

Comment 3 by nxia@chromium.org, Jan 9 2017

Status: Fixed (was: Untriaged)
kefka-release is working well now. The hang might be caused by temporary network/IO problems. Close it for now. 

Comment 4 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 5 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 6 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 7 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 8 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment