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

Issue 830259 link

Starred by 4 users
Status: Fixed
Owner:
█ huangml@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
marq@chromium.org
eugene...@chromium.org
justincohen@chromium.org
olivierrobin@chromium.org
sergeybe...@chromium.org
jbudorick@chromium.org
ios-bugs-priority@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug



Sign in to add a comment

isolate.shard EarlGrey test failing

Project Member Reported by thestig@chromium.org, Apr 8 2018 
https://ci.chromium.org/buildbot/tryserver.chromium.mac/ios-simulator/ is currently full of red try jobs. This is preventing commits from going through CQ.

e.g. https://ci.chromium.org/buildbot/tryserver.chromium.mac/ios-simulator/429659
https://ci.chromium.org/buildbot/tryserver.chromium.mac/ios-simulator/429656

The error output from the failing step on the bots is:

/b/build/slave/cache/xcode_ios_9c40b.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump: '/b/build/slave/ios-simulator/build/src/out/Debug-iphonesimulator/ios_chrome_ui_egtests.app/ios_chrome_ui_egtests': No such file or directory
step returned non-zero exit code: 1

Comment 1 by tkent@chromium.org, Apr 9 2018

Components: Infra>Client>iOS
My wild guess is that:
 - A Great Blink mv CL updated get_landmines.py. So try bots removed all executable files.
 - Many of CLs don't touch iOS files. ios-simulator try bots don't build ios_chrome_ui_egtests
 - However, ios-simulator try bots try to run ios_chrome_ui_egtests?

Comment 2 by olivierrobin@chromium.org, Apr 9 2018

Cc: justincohen@chromium.org
Owner: eugene...@chromium.org
Assigning to sheriff.
CCing people who may have some idea

Comment 3 by olivierrobin@chromium.org, Apr 9 2018 

The analyxe step conclusion is "no depdendency", so no compilation is done.

Comment 4 by olivierrobin@chromium.org, Apr 9 2018

Cc: eugene...@chromium.org
Owner: ----
I think the scenario in #1 is correct.
In my opinion, the bug is in the recipes.
If the analyse determines that there is no compilation required, tests should not run.

Comment 5 by thestig@chromium.org, Apr 9 2018

Labels: -Pri-1 Pri-2
We are down to ~7% failed try jobs. Downgrading priority.

Comment 6 by pkl@chromium.org, Apr 9 2018

Owner: eugene...@chromium.org
Status: Assigned (was: Untriaged)
=> eugenebut as sheriff

Comment 7 by eugene...@chromium.org, Apr 9 2018

Cc: sergeybe...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
Is this something that infra team can triage and/or fix?

Comment 8 by sergeybe...@chromium.org, Apr 10 2018

Components: -Infra>Client>iOS Infra>Client>Chrome
Possibly. I'll be looking into the ios recipe today (for other reasons), and will keep this in mind. But keeping the bug untriaged for others to look at.

Comment 9 by jbudorick@chromium.org, Apr 13 2018

Cc: jbudorick@chromium.org
 Issue 832483  has been merged into this issue.

Comment 10 by jbudorick@chromium.org, Apr 13 2018

Labels: -Pri-2 Pri-1
Status: Available (was: Untriaged)
This is definitely something we should address, and soon.

Comment 11 by jbudorick@chromium.org, Apr 13 2018

Owner: huangml@chromium.org
Status: Assigned (was: Available)
Project Member

Comment 12 by bugdroid1@chromium.org, Apr 13 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/f70a894ebc124e398f3fd25924dc009912ae2a38

commit f70a894ebc124e398f3fd25924dc009912ae2a38
Author: Menglu Huang <huangml@chromium.org>
Date: Fri Apr 13 23:58:31 2018

Skip isolate.shard EarlGrey test when no binary is built

Bug:  830259 
Change-Id: I2330c8888abbce56a478bac8dfcf0cc62359a71b
Reviewed-on: https://chromium-review.googlesource.com/1013146
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Menglu Huang <huangml@chromium.org>

[modify] https://crrev.com/f70a894ebc124e398f3fd25924dc009912ae2a38/scripts/slave/recipe_modules/ios/api.py

Comment 13 by huangml@chromium.org, Apr 14 2018

Status: Fixed (was: Assigned)

Comment 14 by sergeybe...@chromium.org, Apr 16 2018 

The issue is not really fixed - there is still a bug apparently in the analyze recipe code itself. Tracked in issue 833498.

Comment 15 by huangml@chromium.org, Apr 16 2018 

issue 833498 seems like a separate issue about the concern of the analyze step.  The issue of the isolate.shard EarlGrey step is fixed.
►

Sign in to add a comment