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

Issue 704142 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

background:search:google failing with Tap position is off-screen

Project Member Reported by perezju@chromium.org, Mar 22 2017

Issue description

This is happening on the android-one bot, most commonly on background:search:google but also on background:news:nytimes.

Stats on latest builds:

                config                     story                status  expected  failed  missing  matches
1   android-one common   background:news:nytimes  -1------------??----        20       1        2        1
2   android-one common  background:search:google  -1--------1---??----        20       2        2        2
57  android-one memory   background:news:nytimes  -1----?-----------??        60       1        9        1
58  android-one memory  background:search:google  33----?-33----2--3??        60      17        9       17

(numbers in status show how many times this error happened in a story run)


Example traceback:
  File "/b/c/b/Android_One_Perf__1_/src/third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py", line 296, in TapElement
    selector=selector, text=text, element_function=element_function))
[...]
  File "/b/c/b/Android_One_Perf__1_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_runtime.py", line 54, in Evaluate
    description=details.get('exception', {}).get('description'))
EvaluateException: UncaughtError:
Error: Tap position is off-screen
    at TapAction.start (<anonymous>:59:13)
    at callback (<anonymous>:9:30)
    at <anonymous>:17:16
    at <anonymous>:18:9

build: https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20One%20Perf%20%281%29/5073
logdog: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf__1_%2F5073%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile%2F0%2Fstdout

Not sure if the screen shot shows something useful:
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_1-2017-03-21_15-11-4557230.png

+hector could you have a look?
 
Cc: -nednguyen@chromium.org nedngu...@google.com
Components: Tests>Telemetry

Comment 2 by hjd@chromium.org, Mar 23 2017

:( Seems like classic flaky scroll bug. I'm surprised since the button seems to be visible in the screenshot.

Comment 3 by hjd@chromium.org, Mar 23 2017

So I borrowed a Android One device and tried running the story (both alone and with the other background ones) several times but it passed consistently :( Will try to make sure I have the right Android version tomorrow.
Components: -Tests>Telemetry Speed>Benchmarks
Ping, any update on this?
Status: WontFix (was: Assigned)
Sound like there was some transient issue with Chrome. This is no longer happening in bots.

Comment 7 by hjd@chromium.org, Apr 5 2017

My favorite bugs are the ones that fix themselves.

Sorry Ned I missed your ping :( In case anyone ever wonders I never ended up looking any further at this.
 

Sign in to add a comment