org.chromium.chrome.browser.SmartClipProviderTest#testSmartClipDataCallback fails on Marshmallow Tablet Tester |
||||
Issue descriptionThis test fails consistently on Marshmallow Tablet Tester. flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=chrome_public_test_apk&tests=org.chromium.chrome.browser.SmartClipProviderTest%23testSmartClipDataCallback&showExpectations=true Example builds: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Marshmallow%20Tablet%20Tester/499 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Marshmallow%20Tablet%20Tester/498 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Marshmallow%20Tablet%20Tester/497 stack trace: java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.chromium.chrome.browser.SmartClipProviderTest.testSmartClipDataCallback(SmartClipProviderTest.java:218) 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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:115) 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.ExternalResource$1.evaluate(ExternalResource.java:48) 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:237) at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:48) 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:220) 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:122) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879) CL that added the assert: https://chromium-review.googlesource.com/c/chromium/src/+/762544
,
Jun 18 2018
mahesh: can you take a look? I guess this never passed in tablets before, but there isn't enough bot history to confirm. In the mean time for sheriffs, feel free to disable on tablets
,
Jun 18 2018
Re #2: Thanks for the quick response. I'll disable the test on tablet then.
,
Jun 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bb3a6f95a840fe4cc75756f81afb6248a62bdf62 commit bb3a6f95a840fe4cc75756f81afb6248a62bdf62 Author: Becky Zhou <huayinz@chromium.org> Date: Mon Jun 18 21:37:48 2018 Disable SmartClipProviderTest#testSmartClipDataCallback on tablet TBR=boliu@chromium.org Bug: 853816 Change-Id: Icda147b5735a5bda3abf67e296d870a120b55918 Reviewed-on: https://chromium-review.googlesource.com/1105061 Reviewed-by: Becky Zhou <huayinz@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Commit-Queue: Becky Zhou <huayinz@chromium.org> Cr-Commit-Position: refs/heads/master@{#568171} [modify] https://crrev.com/bb3a6f95a840fe4cc75756f81afb6248a62bdf62/chrome/android/javatests/src/org/chromium/chrome/browser/SmartClipProviderTest.java
,
Jun 19 2018
@boliu: I haven't tested this on a tablet. I will take a look.
,
Jun 25 2018
Removing from sheriff queue since the flaky test has been disabled on tablets.
,
Jun 26 2018
,
Jun 26 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by huayinz@chromium.org
, Jun 18 2018