WebRestrictionsResourceThrottleTest.WillStartRequest_Subresource flaky on Android |
|||
Issue descriptionWebRestrictionsResourceThrottleTest.WillStartRequest_Subresource is extremely flaky in a variety of different ways on Android bots. See: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=components_unittests&tests=WebRestrictionsResourceThrottleTest.WillStartRequest_Subresource For example: UNKNOWN UNKNOWN UNKNOWN on http://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester/builds/11734 UNKNOWN UNKNOWN UNKNOWN on http://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/41213 CRASH CRASH PASS on http://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/8290 Usual failure is: ../../components/web_restrictions/browser/web_restrictions_resource_throttle_unittest.cc:131: Failure Value of: defer Actual: true Expected: false In the cases where it crashes, it first encountered the failure above, then hit: [FATAL:lock_impl_posix.cc(65)] Check failed: rv == 0 (35 vs. 0). Resource deadlock would occur aberent: could you take a look at this?
,
Sep 11 2017
The code this is testing is not currently in use, and may soon be tidied up or removed, so reducing the priority.
,
May 21 2018
Closing as obsolete. It seems very unlikely that we will ever re-enable Unicorn URL filtering in Webview. See also issue 819577 and issue 783183. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, May 3 2017