CTS WebViewClientTest#testShouldOverrideUrlLoadingOnCreateWindow flaking |
|||||||
Issue descriptionFlaking for some time (even before https://codereview.chromium.org/2444073002): https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20CTS%20L-MR1%20%28dbg%29/builds/17189 https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20CTS%20L-MR1%20%28dbg%29/builds/17154 https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20CTS%20L-MR1%20%28dbg%29/builds/17108 https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20CTS%20L-MR1%20%28dbg%29/builds/17028 10-25 00:42:49 I/06ad8849003b6c51: android.webkit.cts.WebViewClientTest#testShouldOverrideUrlLoadingOnCreateWindow FAIL junit.framework.ComparisonFailure: expected:<http://localhost:47148/assets/webkit/page_with_link.html> but was:<null> at junit.framework.Assert.assertEquals(Assert.java:85) at junit.framework.Assert.assertEquals(Assert.java:91) at android.webkit.cts.WebViewClientTest.testShouldOverrideUrlLoadingOnCreateWindow(WebViewClientTest.java:147) at java.lang.reflect.Method.invoke(Native Method) at java.lang.reflect.Method.invoke(Method.java:372) at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214) at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199) at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:115) at junit.framework.TestResult.runProtected(TestResult.java:133) at android.support.test.internal.runner.junit3.DelegatingTestResult.runProtected(DelegatingTestResult.java:90) at junit.framework.TestResult.run(TestResult.java:118) at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:52) at junit.framework.TestCase.run(TestCase.java:124) at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:63) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at android.support.test.internal.runner.junit3.DelegatingTestSuite.run(DelegatingTestSuite.java:103) at android.support.test.internal.runner.junit3.AndroidTestSuite.run(AndroidTestSuite.java:52) at android.support.test.internal.runner.junit3.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:24) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:245) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)
,
Oct 26 2016
I can take a look at this first if it's test related, since I was fixing another CTS and set up scripts to run CTS tests multiple time, merge the result and bisect to handle flaky tests
,
Oct 26 2016
Cool, thanks Yoland!
,
Dec 20 2016
Still flaking mainly on L and N bot, looking into this,
,
Dec 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b89f0113f539b02c742c7eb1588767282dd0ddb6 commit b89f0113f539b02c742c7eb1588767282dd0ddb6 Author: yolandyan <yolandyan@chromium.org> Date: Tue Dec 20 17:58:23 2016 Disable failing and flaky CTS tests Disable WebViewClientTest testShouldOverrideUrlLoadingOnCreateWindow, which has been flaky on L and N bot, and ServiceWorkerClientTest testServiceWorkerClientInterceptCallback, which has been failing on N bot BUG= 659077 , 675809 Review-Url: https://codereview.chromium.org/2590053002 Cr-Commit-Position: refs/heads/master@{#439840} [modify] https://crrev.com/b89f0113f539b02c742c7eb1588767282dd0ddb6/android_webview/tools/cts_config/expected_failure_on_bot.json
,
Feb 6 2018
Transition yoland@'s CTS bugs to aluo@.
,
Mar 13 2018
So, what happened to the investigation here? Do we have a link/pointer to the scripts that run CTS tests multiple times?
,
Mar 13 2018
We should investigate whether this is still a problem after PlzNavigate.
,
Aug 3
> We should investigate whether this is still a problem after PlzNavigate. Sounds like now is the right time to investigate this. Someone should try re-enabling the test to see if it still flakes.
,
Aug 3
Also, miscellaneous shouldOverrideUrlLoading improvements: see issue 855733
,
Aug 6
There's a report in buganiser that this test may now be failing 100% of the time for at least one vendor, instead of just being flaky, so we need to check the status and deal with it ASAP - if it's broken while we've had it disabled for being flaky that may actually be a regression in the real code :(
,
Aug 16
Looped the M version of this test on a nexus 5 and local trunk release build. Passed 200 times over lunch. Maybe I should flash back to L, according to the old bot. Or maybe it's some bad interaction between tests..
,
Aug 16
Flashing back to L bricked the device :(
,
Aug 16
Looking at the test code itself, there doesn't seem to be any guarantee that it works. Test loads frame a, has an iframe b, which opens popup c. It waits for onPageFinished, and then checks that shouldOverrideUrl for popup c is called. Which doesn't seem like it guarantees being called. (And then the rest of the test is commented out due to b/12804986. Maybe should fix that too..) It's been awhile since I've built cts locally...
,
Aug 17
Fixing b/12804986 too
,
Aug 17
aluo: is there a bug to keep all the cts tests running, but don't turn the bot red for maybe flaky ones? maybe pull those out into a separate step on the bot that just warns or something? not running disabled tests at all is pretty bad. and maybe this doesn't actually flake anymore, it's just we don't have data to track this
,
Aug 17
Actually, anyone mind if I just enable this based on #12? What the test is doing (wait for onPageFinished then check url in shoudOverrideUrlLoading) is probably ok, so it's likely that the issue 2 years ago was inside webview itself. A lot of has happened since then, including PlzNavigate, and I guess/hope this doesn't happen anymore.
,
Aug 18
Upoaded that cl here: https://chromium-review.googlesource.com/c/chromium/src/+/1180513
,
Aug 22
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/47ae66897bb9826cc578cc9bcf99e3d997026069 commit 47ae66897bb9826cc578cc9bcf99e3d997026069 Author: Bo Liu <boliu@chromium.org> Date: Wed Aug 22 21:12:50 2018 aw: Enable testShouldOverrideUrlLoadingOnCreateWindow Did not flake locally. Bug: 659077 Change-Id: I8770032fb0944b32950987f5674583cf4b4241aa Reviewed-on: https://chromium-review.googlesource.com/1180513 Reviewed-by: Richard Coles <torne@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#585248} [modify] https://crrev.com/47ae66897bb9826cc578cc9bcf99e3d997026069/android_webview/tools/cts_config/expected_failure_on_bot.json
,
Aug 23
bots are pretty happy |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ntfschr@chromium.org
, Oct 26 2016Status: Assigned (was: Available)