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

Issue 803081 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

android.webkit.cts.WebViewTest#testFlingScroll fails with timeout

Project Member Reported by alexilin@chromium.org, Jan 17 2018

Issue description

[FAIL] android.webkit.cts.WebViewTest#testFlingScroll:
junit.framework.AssertionFailedError: unexpected timeout
    at junit.framework.Assert.fail(Assert.java:50)
    at android.cts.util.PollingCheck.run(PollingCheck.java:56)
    at android.webkit.cts.WebViewTest.testFlingScroll(WebViewTest.java:1732)
    at java.lang.reflect.Method.invoke(Native Method)
    at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
    at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
    at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
    at junit.framework.TestCase.runBare(TestCase.java:134)
    at junit.framework.TestResult$1.protect(TestResult.java:115)
    at android.support.test.internal.runner.junit3.AndroidTestResult.runProtected(AndroidTestResult.java:77)
    at junit.framework.TestResult.run(TestResult.java:118)
    at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:55)
    at junit.framework.TestCase.run(TestCase.java:124)
    at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:63)
    at junit.framework.TestSuite.runTest(TestSuite.java:243)
    at junit.framework.TestSuite.run(TestSuite.java:238)
    at android.support.test.internal.runner.junit3.DelegatingTestSuite.run(DelegatingTestSuite.java:103)
    at android.support.test.internal.runner.junit3.AndroidTestSuite.run(AndroidTestSuite.java:69)
    at android.support.test.internal.runner.junit3.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
    at org.junit.runners.Suite.runChild(Suite.java:128)
    at org.junit.runners.Suite.runChild(Suite.java:24)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:136)
    at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)
    at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:228)
    at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879) 

The CTS test is failing on the Android WebView M (dbg). I couldn't reproduce the timeout locally but looking at the time when the issue appeared I suspect the change https://chromium.googlesource.com/chromium/src.git/+/dfd1d101cc43215dbcf9fea18f60ad790bcea691. (from this range: https://chromium.googlesource.com/chromium/src.git/+log/f9b80179d29029e7b785717ad4149618e46b4ff0..a31c7883465702478d93dcf97a4d4144167958e1)

jamwalla@, can you take a look?

May be related to  https://crbug.com/800941 
 

Comment 1 by boliu@chromium.org, Jan 17 2018

hmm, probably that, but weird it's failing only on M, but not L or N. will take a look when I get in

Comment 2 by boliu@chromium.org, Jan 17 2018

this has to do with flingScroll call, which just sends synthesized gesture events down, and then testing scroll indeed changed. hmm, not totally obvious how that breaks, if human flinging didn't break :/

Comment 3 by boliu@chromium.org, Jan 17 2018

Owner: jamwalla@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by torne@chromium.org, Jan 24 2018

Labels: -sheriff-android
James, are you looking at this?

Comment 6 by torne@chromium.org, Jan 24 2018

Status: Fixed (was: Assigned)
Closing this then
Cc: dtapu...@chromium.org tdres...@chromium.org
Owner: sahel@chromium.org
Status: Assigned (was: Fixed)
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20WebView%20L%20%28dbg%29

This test is failing again, I think it's related to crbug.com/807939 and crbug.com/808929. I recently had to try to reproduce this test, so let me know if I can help with debugging. The synthesized gesture events break a lot easier than real life ones.
Cc: dtrainor@chromium.org changwan@chromium.org

Comment 9 by boliu@chromium.org, Feb 7 2018

jamwalla: can you add an equivalent instrumentation test so regressions like this don't happen in the future
I'll work on updating TestFlingScroll (https://cs.corp.google.com/clankium/src/android_webview/javatests/src/org/chromium/android_webview/test/AndroidScrollIntegrationTest.java?q=testflingscroll&l=571&dr=CSs) so that this fails on CQ. The CTS test has been failing every once in a while for the last couple of days, I wonder if that can be improved as well.

Comment 11 by sahel@chromium.org, Feb 13 2018

Status: WontFix (was: Assigned)
https://chromium-review.googlesource.com/c/chromium/src/+/909699 should fix the regression

Sign in to add a comment