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

Issue 709126 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
No longer actively working on Chrom...
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug



Sign in to add a comment

Evaluate and re-enable testEvictedTabReloadFailure if necessary

Project Member Reported by liaoyuke@chromium.org, Apr 6 2017

Issue description

testEvictedTabReloadFailure is flaky on devices because it relies on external URL, and this test fails reliably when running on devices with WIFI turned off.
 
Hi Louis,

I assigned this to you because you are the owner of ios/chrome/browser/metrics.

Please re-assign if necessary.
Please evaluated if this test can be converted to not rely on external URL, if not, maybe considering moving this test to ExternalURLTestCase.
Labels: -Pri-3 Pri-1
Cc: cma...@chromium.org

Comment 5 by cma...@chromium.org, Apr 10 2017

Louis any update? Please add your assessment
Cc: eugene...@chromium.org
Status: Started (was: Assigned)
Eugene, maybe you will know.

The test is basically loading an invalid URL, but expects the error page to be about "This site can’t be reached", but since the network is down, the "There is no Internet connection" takes precedence.

I guess this is expected in the logic of the loading errors? Can it be faked/bypassed?
Otherwise, the solution is to move the test to externalURL, as it really depends on the network.

Thanks!

Comment 7 by baxley@chromium.org, Apr 14 2017

I think liaoyuke@ (cc'd) has encountered this, as part of Wi-Fi problems on our bots.
Actually, I filed this bug. https://bugs.chromium.org/p/chromium/issues/detail?id=694662 is discussing a solution to fake error page, and that's maybe what you are looking for.
Cc: huangml@chromium.org
Menglu is trying to understand if we can trigger WKWebView's error, w/o actually using network  crbug.com/694662 . 
Blockedon: 694662
Status: Fixed (was: Started)
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-59; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-59 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD Merge-Request-59
Blockedon: -694662
Removing "Blocked on"  issue 694662 . It's related but not blocking anymore.
Project Member

Comment 16 by sheriffbot@chromium.org, May 2 2017

Labels: -Merge-Request-59 Hotlist-Merge-Approved Merge-Approved-59
Your change meets the bar and is auto-approved for M59. Please go ahead and merge the CL to branch 3071 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 17 by bugdroid1@chromium.org, May 2 2017

Louis,
are there any test steps to verify this issue manually, thanks.
$ python ios_internal/tools/tests/failed_tests_history.py -t ExternalURLTabUsageRecorderTestCase.testEvictedTabReloadFailure -l 22

returns nothing. I tried with higher values of |limit| and HTTP_REQUEST_TIME_OUT_SECONDS, but it fails like this:

$ python ios_internal/tools/tests/failed_tests_history.py -t ExternalURLTabUsageRecorderTestCase.testEvictedTabReloadFailure -l 25
HTTP error at HTTP Error 500: Internal Server Error
Reduce |limit| or increase |HTTP_REQUEST_TIME_OUT_SECONDS|

We haven't seen this test fail again, so I'd consider it verified on trunk. I am not sure how to check easily on the branch apart looking at the logs on the branch since the cherry-pick.
Components: Tests>Disabled
Labels: Test-Disabled

Sign in to add a comment