New issue
Advanced search Search tips

Issue 810148 link

Starred by 1 user
Status: Started
Owner:
sahel@chromium.org
Cc:
kenrb@chromium.org
boliu@chromium.org
sahel@chromium.org
stale-flakes-reports@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

"org.chromium.content.browser.ContentViewScrollingTest#testFling" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 7 2018 
"org.chromium.content.browser.ContentViewScrollingTest#testFling" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySgsSBUZsYWtlIj9vcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLkNvbnRlbnRWaWV3U2Nyb2xsaW5nVGVzdCN0ZXN0RmxpbmcM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by olka@chromium.org, Feb 8 2018 

https://ci.chromium.org/buildbot/tryserver.chromium.android/linux_android_rel_ng/483597

java.lang.AssertionError: Criteria not met in allotted time.
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:93)
	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:108)
	at org.chromium.content.browser.ContentViewScrollingTest.waitForScroll(ContentViewScrollingTest.java:99)
	at org.chromium.content.browser.ContentViewScrollingTest.testFling(ContentViewScrollingTest.java:212)
	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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37)
	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:201)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:43)
	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:183)
	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:99)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

Comment 2 by olka@chromium.org, Feb 8 2018

Cc: boliu@chromium.org
Labels: OS-Android

Comment 3 by mcnee@chromium.org, Feb 8 2018

Cc: kenrb@chromium.org sahel@chromium.org
cc'ing sahel@ for any thoughts on this.

We also have a known issue where scrolling stalls on android (crbug.com/806940) due to coalescing of touch events in RenderWidgetTargeter, but I'm not sure if that would affect this.

Comment 4 by treib@chromium.org, Feb 12 2018

Labels: -Sheriff-Chromium
Looks like this hasn't flaked in the last ~4 days, so taking out of the sheriff queue.
Project Member

Comment 5 by chromium...@appspot.gserviceaccount.com, Jul 13

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "org.chromium.content.browser.ContentViewScrollingTest#testFling". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySgsSBUZsYWtlIj9vcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLkNvbnRlbnRWaWV3U2Nyb2xsaW5nVGVzdCN0ZXN0RmxpbmcM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 6 by sahel@chromium.org, Jul 13

Owner: sahel@chromium.org
Status: Assigned (was: Untriaged)
I'll investigate it

Comment 7 by sahel@chromium.org, Jul 13 

The new flakes are on android-marshmallow-arm64-rel, is there anything specific about this bot?

Comment 8 by boliu@chromium.org, Jul 13 

It's using nexus 5x with android M
Project Member

Comment 9 by chromium...@appspot.gserviceaccount.com, Jul 20

Cc: stale-flakes-reports@google.com
Reporting to stale-flakes-reports@google.com to investigate why this issue is not being processed despite being in an appropriate queue for 7 days or more.

Comment 10 by sahel@chromium.org, Jul 23

Status: Started (was: Assigned)
https://chromium-review.googlesource.com/c/chromium/src/+/1140912 might fix the issue, I'll see if the flakiness still exists after landing this cl.

Comment 11 by hajimehoshi@chromium.org, Jul 25

Labels: -Sheriff-Chromium
Project Member

Comment 12 by chromium...@appspot.gserviceaccount.com, Sep 10

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "org.chromium.content.browser.ContentViewScrollingTest#testFling". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySgsSBUZsYWtlIj9vcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLkNvbnRlbnRWaWV3U2Nyb2xsaW5nVGVzdCN0ZXN0RmxpbmcM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 13 by yhirano@chromium.org, Sep 11

Labels: -Sheriff-Chromium
Removing Sheriff-Chromium as there is an owner.
►

Sign in to add a comment