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

Issue 767180 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

webview_instrumentation_test_apk failing on chromium.android/Android N5X Swarm Builder

Project Member Reported by sgu...@chromium.org, Sep 20 2017

Issue description

webview_instrumentation_test_apk failing on chromium.android/Android N5X Swarm Builder

Builders failed on: 
- Android N5X Swarm Builder: 
  https://build.chromium.org/p/chromium.android/builders/Android%20N5X%20Swarm%20Builder



This is likely a flake (but I did not wait long enough to see if the failure went away yet). 
The stack is:

org.junit.ComparisonFailure: expected:<[Has databas]e> but was:<[Non]e>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at org.chromium.android_webview.test.AwSettingsTest$AwSettingsDatabaseTestHelper.doEnsureSettingHasValue(AwSettingsTest.java:610)
	at org.chromium.android_webview.test.AwSettingsTest$AwSettingsDatabaseTestHelper.doEnsureSettingHasValue(AwSettingsTest.java:572)
	at org.chromium.android_webview.test.AwSettingsTest$AwSettingsTestHelper.ensureSettingHasValue(AwSettingsTest.java:162)
	at org.chromium.android_webview.test.AwSettingsTest$AwSettingsTestHelper.ensureSettingHasAlteredValue(AwSettingsTest.java:110)
	at org.chromium.android_webview.test.AwSettingsTest.testDatabaseEnabled(AwSettingsTest.java:1829)
	at java.lang.reflect.Method.invoke(Native Method)
	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:55)
	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:175)
	at org.chromium.android_webview.test.AwJUnit4ClassRunner.runChild(AwJUnit4ClassRunner.java:61)
	at org.chromium.android_webview.test.AwJUnit4ClassRunner.runChild(AwJUnit4ClassRunner.java:28)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:164)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:98)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)

Searching for native crashes in: /b/swarming/w/it4yQMgi/tmp4y2jz_
Unknown Android release, consider passing --packed-lib.
Reading Android symbols from: /b/swarming/w/ir
Searching for Chrome symbols from within: /b/swarming/w/ir/out/Release/lib.unstripped:/b/swarming/w/ir/out/Release/lib:/b/swarming/w/ir/out/Release



 

Comment 1 by sgu...@chromium.org, Sep 20 2017

Components: Mobile>WebView

Comment 3 by sgu...@chromium.org, Sep 21 2017

Cc: bauerb@chromium.org jbudorick@chromium.org
The same bot next failing in content unittests and then in gl tests. seems to be timing out.



WARNING:root:task_output_dir '/tmp/tmp8mOBb6' already exists!
WARNING:root:task_output_dir existing content: []
Waiting for results from the following shards: 0
Waiting for results from the following shards: 0
Waiting for results from the following shards: 0
+------------------------------------------------------------------------+
| Shard 0  https://chromium-swarm.appspot.com/user/task/38ba4bbf5d5ee310 |
|  Pending: 0.8s  Duration: 3600.0s  Bot: build327-m4--device6  Exit: 1  |
+------------------------------------------------------------------------+
Total duration: 3600.0s
WARNING:root:collect_cmd had non-zero return code: 1
step returned non-zero exit code: 1
Owner: torne@chromium.org
Status: Assigned (was: Available)
torne@, can you take a peek at why this might be happening?
#3: that's a different issue: https://bugs.chromium.org/p/chromium/issues/detail?id=721889

Comment 6 by sgu...@chromium.org, Sep 21 2017

Status: WontFix (was: Assigned)
the bot is now green.
Labels: Pri-1
Status: Assigned (was: WontFix)
This happened again:

https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20N5X%20Swarm%20Builder/builds/15416

This test is flaky and needs to be fixed or disabled. Torne, can you fix or route this?

Comment 9 by treib@chromium.org, Sep 26 2017

I'm disabling the flaky test.

Comment 10 by treib@chromium.org, Sep 26 2017

Flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webview_instrumentation_test_apk&tests=org.chromium.android_webview.test.AwSettingsTest%23testDatabaseEnabled

It's failing maybe 1 out of 10 runs on Android N5X Swarm, and less frequently on some others.
Project Member

Comment 11 by bugdroid1@chromium.org, Sep 26 2017

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

commit 6cb262dd1ed0aaef6076911b7d672a6303a29548
Author: Marc Treib <treib@chromium.org>
Date: Tue Sep 26 14:08:03 2017

Disable flaky AwSettingsTest.testDatabaseEnabled

TBR=torne@chromium.org

Bug:  767180 
Change-Id: I3ad4f6d1b67d19eb09f5dd489699031d629ff740
Reviewed-on: https://chromium-review.googlesource.com/684375
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#504356}
[modify] https://crrev.com/6cb262dd1ed0aaef6076911b7d672a6303a29548/android_webview/javatests/src/org/chromium/android_webview/test/AwSettingsTest.java

Comment 12 by treib@chromium.org, Sep 26 2017

Components: Tests>Flaky Tests>Disabled
Labels: -Sheriff-Chromium OS-Android
Taking out of the sheriff queue.

Comment 13 by boliu@chromium.org, Sep 26 2017

Cc: ctzsm@chromium.org
 Issue 767467  has been merged into this issue.
Project Member

Comment 14 by bugdroid1@chromium.org, Nov 17 2017

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

commit 44aedd6c453493dadb33bfdd79a99e0743d48d05
Author: Shimi Zhang <ctzsm@chromium.org>
Date: Fri Nov 17 19:14:12 2017

aw: Enable AwSettingsTest.testDatabaseEnabled

I did about 800 run on Nexus 5x on Android N and 200 run on Pixel on
Android master, all of them passed, so try to reenable it.

Bug:  767180 
Change-Id: Ie373a37271aabb5008ac700ff29779f134e5faea
Reviewed-on: https://chromium-review.googlesource.com/776206
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517504}
[modify] https://crrev.com/44aedd6c453493dadb33bfdd79a99e0743d48d05/android_webview/javatests/src/org/chromium/android_webview/test/AwSettingsTest.java

Comment 15 by ctzsm@chromium.org, Nov 17 2017

Cc: -ctzsm@chromium.org
Owner: ctzsm@chromium.org
Start to monitor this test in flakiness dashboard.
Project Member

Comment 16 by bugdroid1@chromium.org, Dec 5 2017

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

commit 3f3ee3e4a665e58bd7a6bc6d173f209e3dd8b040
Author: Shimi Zhang <ctzsm@chromium.org>
Date: Tue Dec 05 16:58:31 2017

aw: remove @RetryOnFailure for AwSettingsTest#testDatabaseEnabled

Flakiness dashboard looks green, so remove @RetryOnFailure.

Bug:  767180 
Change-Id: I62d513b6c89836af85bf6933bdef18f6e9df468c
Reviewed-on: https://chromium-review.googlesource.com/806318
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521722}
[modify] https://crrev.com/3f3ee3e4a665e58bd7a6bc6d173f209e3dd8b040/android_webview/javatests/src/org/chromium/android_webview/test/AwSettingsTest.java

Status: Fixed (was: Assigned)
Components: Tests>Disabled
Labels: Test-Disabled

Sign in to add a comment