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

Issue 694415 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Dartium gyp run on MacOS now hangs, was 5 minutes

Project Member Reported by whesse@chromium.org, Feb 21 2017

Issue description

Our buildbot MacOS bot that builds Dartium is now failing, because the runhooks step that took 5 minutes is now taking more than 40 minutes.
The builder that is failing is https://uberchromegw.corp.google.com/i/client.dart/builders/dartium-mac-x64-inc-be


We are building Dartium based on Chrome 45, using gyp (I know, this is very very old, but it needs to work.  We are moving up to version 50 in weeks).

The bot runs, as part of the runhooks step, src/build/gyp_chromium' which took 303.54 secs

In the next build, and thereafter, the src/build/gyp_chromium step takes 40 minutes, and then the buildbot step times out.

Nothing changed in the dartium build, so I am wondering if software changes in the build directory maintained by chrome-infra could have caused this to happen.  The hash of the last working build directory release is
45191f3bfdf590993582f180df558b70d37ae710
and the first failing build directory release is 
04badb9796f8a7343ac7360203b367c1c976360b

We need to get this fixed somehow, so if someone with knowledge of gyp_chromium could help out, or from build or infra has any ideas, please help.
 

Comment 1 by whesse@google.com, Feb 21 2017

Status: Fixed (was: Untriaged)
The problem was resolved by rebooting the build slave.
Please ignore.

Sign in to add a comment