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

Issue 679979 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Occasional test time out on ios-simulator

Project Member Reported by timloh@chromium.org, Jan 11 2017

Issue description

The ios-simulator bot seems to be occasionally timing out tests that otherwise take <10s.

https://build.chromium.org/p/chromium.mac/builders/ios-simulator?numbuilds=200

Seven failures in the last 200 builds:
Failed steps failed ios_net_unittests (ipad air 2 ios 10.0)
Failed steps failed gfx_unittests (ipad air 2 ios 10.0)
Failed steps failed gfx_unittests (ipad air 2 ios 10.0)
Failed steps failed google_apis_unittests (ipad air 2 ios 10.0)
Failed steps failed sql_unittests (ipad air 2 ios 10.0)
Failed steps failed ios_chrome_unittests (ipad air 2 ios 10.0)
Failed steps failed components_unittests (iphone 6s ios 10.0)

 
Status: Available (was: Untriaged)
This seems to happen a few times a week at peak hours: http://shortn/_5ypWTgEdWh (though the peaks might be clumping several failures together)

Looking at a few timed out shards, I see that they were running (so it's not a capacity issue), just running for way too long with no response from the bot. Maybe the bots are dying mid-test and never respond?
 Issue 690746  has been merged into this issue.
Project Member

Comment 3 by chromium...@appspot.gserviceaccount.com, Feb 11 2017

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "google_apis_unittests". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIAsSBUZsYWtlIhVnb29nbGVfYXBpc191bml0dGVzdHMM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 4 by xlai@chromium.org, Feb 13 2017

Cc: stkhapugin@chromium.org
Labels: OS-iOS
It's still happening today. https://build.chromium.org/p/chromium.mac/builders/ios-simulator/builds/14392

I notice that this issue (https://bugs.chromium.org/p/chromium/issues/detail?id=624363) keeps rolling in commits touching tests on ios. Not sure if this is related. stkhapugin@: Mind take a look at it?

Comment 5 by perkj@chromium.org, Feb 15 2017

Labels: -Sheriff-Chromium
Cc: -stkhapugin@chromium.org
This is a bug with tens of commits related to ARC transition, that happen to be tests in the past few weeks but is not limited to tests. I don't think it is related. 
Project Member

Comment 7 by chromium...@appspot.gserviceaccount.com, Mar 31 2017

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "google_apis_unittests". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIAsSBUZsYWtlIhVnb29nbGVfYXBpc191bml0dGVzdHMM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
Labels: -Sheriff-Chromium
Cc: davidben@chromium.org
 Issue 708110  has been merged into this issue.
Labels: -Pri-3 Infra-Troopers Pri-2
Status: Untriaged (was: Available)
Cc: liaoyuke@chromium.org baxley@chromium.org smut@chromium.org rohitrao@chromium.org
It seems like this is caused by flaky tests? Is there any action desired from a trooper here? 

Comment 13 by s...@google.com, Apr 6 2017

Labels: -Infra-Troopers
No trooper action is needed here. The iossim invocations are just hanging.
Another instance today:
https://uberchromegw.corp.google.com/i/chromium.mac/builders/ios-simulator/builds/16338

It doesn't look like any tests were actually run, something in the setup of the device seems to have stalled.
Filed  issue 709374  since it seems different from this issue.
Status: WontFix (was: Untriaged)
Marking this closed. Continue discussion on the new bug in  crbug.com/709374 

Sign in to add a comment