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

Issue 704138 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug



Sign in to add a comment

EarlGrey tests appear to not full load the app

Project Member Reported by baxley@chromium.org, Mar 22 2017

Issue description

About once per 500 runs, the test suite seems to fail to load the application.

For example:
https://build.chromium.org/p/chromium.fyi/builders/EarlGreyiOS/builds/25567/steps/ios_chrome_ui_egtests%20%28iPhone%206s%20iOS%2010.0%29

In this all the screen shots show a black screen. The log statements are working, and the tests are failing to see anything in the UI.

Any JS execution results in this error message: 
"Script execution has failed: JS evaluation failed because there is no web view."
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/54548ddbe9febbe12dafb3178811a0c86b0636f7

commit 54548ddbe9febbe12dafb3178811a0c86b0636f7
Author: baxley <baxley@chromium.org>
Date: Fri Mar 24 03:47:20 2017

Take desktop screenshots after test failures in test_runner.py.

There have been some simulator issues that are hard to debug, where
the simulator is black/blank, or there are system alerts, which the
simulator doesn't have access to in screenshots. Having desktop
screenshots would be a great debugging aid.

BUG= 704138 

Review-Url: https://codereview.chromium.org/2767143003
Cr-Commit-Position: refs/heads/master@{#459356}

[modify] https://crrev.com/54548ddbe9febbe12dafb3178811a0c86b0636f7/ios/build/bots/scripts/test_runner.py

Comment 2 by baxley@chromium.org, Mar 31 2017

After debugging with screenshot after test failures, there appears to be no app running:
https://isolateserver.appspot.com/browse?namespace=default-gzip&digest=35dafd3bb196c3481b3c3187e42277b438461ae7&as=desktop_1490755999.2.png

In the past ~1400 runs this has only occurred on iPhone a few times, and no occurrences on iPad.

Comment 3 by baxley@chromium.org, Mar 31 2017

To be more explicit, there were 9 of these simulator failures out of the last ~1400 iPhone runs. There were 0 failures in the last ~1400 iPad runs.
Status: WontFix (was: Started)
I haven't seen this failure lately, though there may be more timeout errors. We can re-open if this comes back.

Sign in to add a comment