New issue
Advanced search Search tips

Issue 598367 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

DevToolsProtocolTest.SynthesizeScrollGesture and DevToolsProtocolTest.SynthesizeTapGesture flaky on Android "Marshmallow Tablet Tester" bot because the page isn't long enough

Project Member Reported by dfalcant...@chromium.org, Mar 28 2016

Issue description

Can't repro locally, but either one or the other fails on the bots regularly.  Sending to dgozman for triage and maybe get an idea of why it's failing.

I  591.158s run_tests_on_device(0a638c5f)  [==========] Running 1 test from 1 test case.
I  591.158s run_tests_on_device(0a638c5f)  [----------] Global test environment set-up.
I  591.158s run_tests_on_device(0a638c5f)  [----------] 1 test from DevToolsProtocolTest, where TypeParam = 
I  591.158s run_tests_on_device(0a638c5f)  [ RUN      ] DevToolsProtocolTest.SynthesizeTapGesture
I  591.158s run_tests_on_device(0a638c5f)  [WARNING:dns_config_service_posix.cc(306)] Failed to read DnsConfig.
I  591.158s run_tests_on_device(0a638c5f)  [ERROR:devtools_http_handler.cc(229)] Cannot start http server for devtools. Stop devtools.
I  591.158s run_tests_on_device(0a638c5f)  [WARNING:shell.cc(299)] Instance: exe:chrome attempting to register an instance for a process it created for target: exe:chrome_renderer without the mojo:shell{client_process} capability class.
I  591.158s run_tests_on_device(0a638c5f)  [ERROR:layer_tree_host_impl.cc(2205)] Forcing zero-copy tile initialization as worker context is missing
I  591.159s run_tests_on_device(0a638c5f)  [ERROR:shell_android.cc(70)] Not implemented reached in void content::Shell::PlatformSetTitle(const string16&): Synthetic Gesture Test Page
I  591.159s run_tests_on_device(0a638c5f)  referenceTable head length=54 1
I  591.159s run_tests_on_device(0a638c5f)  ../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:333: Failure
I  591.159s run_tests_on_device(0a638c5f)  Expected: (scroll_top) > (0), actual: 0 vs 0
I  591.159s run_tests_on_device(0a638c5f)  [  FAILED  ] DevToolsProtocolTest.SynthesizeTapGesture, where TypeParam =  and GetParam() =  (1192 ms)
I  591.159s run_tests_on_device(0a638c5f)  [----------] 1 test from DevToolsProtocolTest (1192 ms total)
I  591.159s run_tests_on_device(0a638c5f)  
I  591.159s run_tests_on_device(0a638c5f)  [----------] Global test environment tear-down
I  591.159s run_tests_on_device(0a638c5f)  [==========] 1 test from 1 test case ran. (1193 ms total)
I  591.159s run_tests_on_device(0a638c5f)  [  PASSED  ] 0 tests.
I  591.159s run_tests_on_device(0a638c5f)  [  FAILED  ] 1 test, listed below:
I  591.159s run_tests_on_device(0a638c5f)  [  FAILED  ] DevToolsProtocolTest.SynthesizeTapGesture, where TypeParam =  and GetParam() = 

https://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/3356
https://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/3355
https://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/3354
https://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/3353
 
Labels: OS-Android
Er, could this be because the page doesn't scroll down far enough on the page?  I was testing this on landscape versus portrait and it passed fine, but I wonder if the lab bots are running in portrait.
Status: Assigned (was: Untriaged)
Yeah, flakily fails locally when I run it in portrait on my Nexus 7 2013.  Going to disable this pair of tests until a fix lands.
Summary: DevToolsProtocolTest.SynthesizeScrollGesture and DevToolsProtocolTest.SynthesizeTapGesture flaky on Android "Marshmallow Tablet Tester" bot because the page isn't long enough (was: DevToolsProtocolTest.SynthesizeScrollGesture and DevToolsProtocolTest.SynthesizeTapGesture flaky on Android "Marshmallow Tablet Tester" bot)
We've had similar failures in the past where the test proceeded before Android finished laying out the page.  The workaround was to set the page to have a specific page scale factor and then block on reading out the correct value:

https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/android/javatests/src/org/chromium/chrome/test/util/ApplicationTestUtils.java&l=155
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 28 2016

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

commit 6a5d8c1dcb818540fed5dd86c066d6711ea359be
Author: dfalcantara <dfalcantara@chromium.org>
Date: Mon Mar 28 20:37:05 2016

Disable DevToolsProtocolTest.Synthesize*Gesture tests

These are flaking randomly on the Marshmallow Tablet Tester bot
(see the bug for details and a potential workaround).

BUG= 598367 
TBR=dgozman

Review URL: https://codereview.chromium.org/1837813003

Cr-Commit-Position: refs/heads/master@{#383555}

[modify] https://crrev.com/6a5d8c1dcb818540fed5dd86c066d6711ea359be/content/browser/devtools/protocol/devtools_protocol_browsertest.cc

Status: Archived (was: Assigned)

Sign in to add a comment