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

Issue 637139 link

Starred by 3 users
Status: Fixed
Owner:
█ smut@chromium.org
User never visited
Closed: Aug 2016
Cc:
█ phajdan.jr@chromium.org
caseq@chromium.org
ios-bugs-priority@chromium.org
ios-bugs@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug



Sign in to add a comment

"ios-simulator" builder broken.

Project Member Reported by d...@chromium.org, Aug 11 2016 
https://build.chromium.org/p/chromium.mac/builders/ios-simulator

Builds as of Aug 11 14:54 have been failing with bad app path:
step returned non-zero exit code: 2
@@@STEP_TEXT@AppNotFoundError: App does not exist: /b/rr/tmp6Mqsim/w/src/out/Debug-iphonesimulator/base_unittests.app.@@@

smut@ says it's related to recipe/master changes to "remote_run".

Comment 1 by smut@chromium.org, Aug 12 2016

Cc: phajdan.jr@chromium.org
Components: Infra>Client>iOS
Labels: OS-iOS
Status: Started (was: Assigned)
So what happened was that some remote_run-related recipe changes landed that I didn't know about:
https://chromium.googlesource.com/chromium/tools/build.git/+/15eadb86674b47f07b21648deb3302b4c9891357
https://chromium.googlesource.com/chromium/tools/build.git/+/9aa6e0a8124b331eb3c68900172ecbeb293deba3

And then master.chromium.mac and master.tryserver.chromium.mac were updated to use remote_run:
https://chromium.googlesource.com/chromium/tools/build/+/147e7f678124bb714cfacf9775c9bd4cffef17f7
https://chromium.googlesource.com/chromium/tools/build/+/a249241b78fe3297e06b41c5a0f4fac4a0c9b982

Then I realized that this broke ios-simulator-swarming:
https://uberchromegw.corp.google.com/i/tryserver.chromium.mac/builders/ios-simulator-swarming/builds/7

So I reverted the recipe changes and the master.tryserver.chromium.mac change:
https://chromium.googlesource.com/chromium/tools/build/+/a7d2fc32f5b0db4a878246303e1794867ea580e3
https://chromium.googlesource.com/chromium/tools/build/+/b6139b59ce10e1fa4ff94dde91fe4d8c3dd44f4f

But I didn't realize there was a master.chromium.mac change to revert as well:
https://chromium.googlesource.com/chromium/tools/build/+/abf76ba9dbb04054a87c53cd2b5d6297a7c2dacc
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 12 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager.git/+/684061dae30ca500c5e4e8a1ec21830d976df851

commit 684061dae30ca500c5e4e8a1ec21830d976df851
Author: smut <smut@google.com>
Date: Fri Aug 12 00:05:50 2016

Comment 3 by d...@chromium.org, Aug 12 2016

Cc: caseq@chromium.org
+caseq@, who reported the initial outage.

Comment 4 by caseq@chromium.org, Aug 12 2016

Labels: Sheriff-Chromium

Comment 5 by smut@chromium.org, Aug 12 2016

Status: Fixed (was: Started)

Comment 6 by caseq@chromium.org, Aug 12 2016 

 Issue 637143  has been merged into this issue.

Comment 7 by caseq@chromium.org, Aug 12 2016 

 Issue 637227  has been merged into this issue.

Comment 8 by caseq@chromium.org, Aug 12 2016 

 Issue 637193  has been merged into this issue.

Comment 9 by caseq@chromium.org, Aug 12 2016 

 Issue 637214  has been merged into this issue.

Comment 10 by caseq@chromium.org, Aug 12 2016 

 Issue 637387  has been merged into this issue.
►

Sign in to add a comment