AwSettingsTest_testCacheMode__multiprocess_mode is flaky |
||||||||
Issue descriptionExample failures: - https://uberchromegw.corp.google.com/i/chromium.android/builders/KitKat%20Tablet%20Tester/builds/9671 - https://uberchromegw.corp.google.com/i/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/10574 Stack trace: java.lang.AssertionError: expected:<1> but was:<2> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.chromium.android_webview.test.AwSettingsTest.testCacheMode(AwSettingsTest.java:2333) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.chromium.android_webview.test.AwActivityTestRule$1.evaluate(AwActivityTestRule.java:72) at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55) at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:184) at org.chromium.android_webview.test.AwJUnit4ClassRunner.runChild(AwJUnit4ClassRunner.java:66) at org.chromium.android_webview.test.AwJUnit4ClassRunner.runChild(AwJUnit4ClassRunner.java:33)
,
Nov 20 2017
Why are we running multiprocess mode tests on KitKat/Lollipop devices..? I guess providing that flag won't change the setup at all anyway..
,
Nov 20 2017
This is still flaking every now and then, especially on Lollipop Tablet Tester. John, how do I know what device this bot is using? (it feels like that should be easy to find out but I can't find it from the buildbot page :/).
,
Nov 20 2017
Using https://uberchromegw.corp.google.com/i/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/10574 as an example -- if you drill into the swarming task that failed (https://chromium-swarm.appspot.com/task?id=399901bac35f0810), you can see device type & OS (N7v2 and LMY49B)
,
Nov 20 2017
> Why are we running multiprocess mode tests on KitKat/Lollipop devices..? I guess providing that flag won't change the setup at all anyway.. Keep in mind this isn't the "real webview", it's the instrumentation test shell. Setting the multiprocess flag most definitely causes it to spin up renderer processes.
,
Dec 4 2017
Note this is still causing pain for sheriffs.
,
Dec 4 2017
,
Dec 4 2017
########### copied from issue 791505 ################# Also testExitFullscreenEndsIfAppInvokesCallback.*__multiprocess_mode https://uberchromegw.corp.google.com/i/chromium.android/builders/Lollipop%20Phone%20Tester/builds/17057
,
Dec 8 2017
,
Feb 15 2018
Is anyone looking into fixing this issue? John who should be the best owner?
,
Feb 15 2018
,
Feb 15 2018
re #10, as mentioned out of band: one of the webview folks would know better than I do.
,
Apr 9 2018
assigning to Nate - might be related to ShouldBlockRequest() logic or network caching logic. Could you take a look?
,
Apr 11 2018
,
Jun 19 2018
Can't find any flakes on try-flakes: https://chromium-try-flakes.appspot.com/search?q=org.chromium.android_webview.test.AwSettingsTest.testCacheMode I assume this means it's not flaking anymore? |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by wychen@chromium.org
, Nov 13 2017