RestoreHistogramTest.testWritingHistogramAtStartup is flaky. |
||
Issue descriptionhttps://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20CFI/2539 I 955.349s run_tests_on_device(01e2b99e0bd1a830) 1) testWritingHistogramAtStartup(org.chromium.chrome.browser.RestoreHistogramTest) I 955.350s run_tests_on_device(01e2b99e0bd1a830) java.lang.AssertionError: expected:<1> but was:<0> I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.Assert.fail(Assert.java:88) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.Assert.failNotEquals(Assert.java:834) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.Assert.assertEquals(Assert.java:645) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.Assert.assertEquals(Assert.java:631) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.chrome.browser.RestoreHistogramTest.testWritingHistogramAtStartup(RestoreHistogramTest.java:109) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at java.lang.reflect.Method.invoke(Method.java) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:116) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.rules.RunRules.evaluate(RunRules.java:20) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:237) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:48) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:220) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.Suite.runChild(Suite.java:128) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.Suite.runChild(Suite.java:27) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:125) I 955.350s run_tests_on_device(01e2b99e0bd1a830) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)
,
Aug 17
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ba042db109e0fc457f3a421bd6f0bb62b4ddee07 commit ba042db109e0fc457f3a421bd6f0bb62b4ddee07 Author: Findit <findit-for-me@appspot.gserviceaccount.com> Date: Fri Aug 17 19:41:04 2018 Revert "Disable flaky RestoreHistogramTest testWritingHistogramAtStartup." This reverts commit 434f3432590888b898ce85fdb99eabfbb2d59f72. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 584133 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzQzNGYzNDMyNTkwODg4Yjg5OGNlODVmZGI5OWVhYmZiYjJkNTlmNzIM Sample Failed Build: https://ci.chromium.org/buildbot/chromium/android-rel/738 Sample Failed Step: compile Original change's description: > Disable flaky RestoreHistogramTest testWritingHistogramAtStartup. > > TBR=tedchoc@chromium.org > NOTRY=true (disabling a test) > > Bug: 875372 > Change-Id: Ia51964a62207de7300b159e80a3e4816af8f579b > Reviewed-on: https://chromium-review.googlesource.com/1180165 > Reviewed-by: apacible <apacible@chromium.org> > Commit-Queue: apacible <apacible@chromium.org> > Cr-Commit-Position: refs/heads/master@{#584133} Change-Id: Ib147d1b5da422966072e141e1612b571aaf29587 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 875372 Reviewed-on: https://chromium-review.googlesource.com/1180263 Cr-Commit-Position: refs/heads/master@{#584151} [modify] https://crrev.com/ba042db109e0fc457f3a421bd6f0bb62b4ddee07/chrome/android/javatests/src/org/chromium/chrome/browser/RestoreHistogramTest.java
,
Aug 17
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/02781f62be65db0e7bf4035fda3511897da78724 commit 02781f62be65db0e7bf4035fda3511897da78724 Author: Jennifer Apacible <apacible@chromium.org> Date: Fri Aug 17 20:21:27 2018 Disable flaky RestoreHistogramTest testWritingHistogramAtStartup. Relanding to fix compiler error. TBR=tedchoc@chromium.org NOTRY=true (disabling a test) Bug: 875372 Change-Id: Idc4c7863dd6e8e1d97ec974c2b8dff3fd09d91f1 Reviewed-on: https://chromium-review.googlesource.com/1180268 Commit-Queue: apacible <apacible@chromium.org> Reviewed-by: apacible <apacible@chromium.org> Cr-Commit-Position: refs/heads/master@{#584171} [modify] https://crrev.com/02781f62be65db0e7bf4035fda3511897da78724/chrome/android/javatests/src/org/chromium/chrome/browser/RestoreHistogramTest.java
,
Aug 22
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Aug 17