All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=633489

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyzQELEhNTdG9wcGFnZUFsZXJ0UGFyZW50Ip4BQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM5L3Ntb290aG5lc3Muc3luY19zY3JvbGwua2V5X21vYmlsZV9zaXRlc19zbW9vdGgvZnJhbWVfdGltZXMvaHR0cF9fX3d3dy5jbm4uY29tXzIwMTJfMTBfMDNfcG9saXRpY3NfbWljaGVsbGUtb2JhbWEtZGViYXRlX2luZGV4Lmh0bWwMCxINU3RvcHBhZ2VBbGVydBib6BgM,agxzfmNocm9tZXBlcmZy5QELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrYBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM5L3Ntb290aG5lc3Muc3luY19zY3JvbGwua2V5X21vYmlsZV9zaXRlc19zbW9vdGgvZmlyc3RfZ2VzdHVyZV9zY3JvbGxfdXBkYXRlX2xhdGVuY3kvaHR0cF9fX3d3dy5jbm4uY29tXzIwMTJfMTBfMDNfcG9saXRpY3NfbWljaGVsbGUtb2JhbWEtZGViYXRlX2luZGV4Lmh0bWwMCxINU3RvcHBhZ2VBbGVydBjJxxgM,agxzfmNocm9tZXBlcmZy6QELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IroBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM5L3Ntb290aG5lc3Muc3luY19zY3JvbGwua2V5X21vYmlsZV9zaXRlc19zbW9vdGgvZmlyc3RfZ2VzdHVyZV9zY3JvbGxfdXBkYXRlX2xhdGVuY3kvaHR0cF9fX3d3dy5jbm4uY29tXzIwMTJfMTBfMDNfcG9saXRpY3NfbWljaGVsbGUtb2JhbWEtZGViYXRlX2luZGV4Lmh0bWxfcmVmDAsSDVN0b3BwYWdlQWxlcnQYyccYDA,agxzfmNocm9tZXBlcmZy2gELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IqsBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM5L3Ntb290aG5lc3Muc3luY19zY3JvbGwua2V5X21vYmlsZV9zaXRlc19zbW9vdGgvbWVhbl9pbnB1dF9ldmVudF9sYXRlbmN5L2h0dHBfX193d3cuY25uLmNvbV8yMDEyXzEwXzAzX3BvbGl0aWNzX21pY2hlbGxlLW9iYW1hLWRlYmF0ZV9pbmRleC5odG1sDAsSDVN0b3BwYWdlQWxlcnQYyccYDA,agxzfmNocm9tZXBlcmZy3gELEhNTdG9wcGFnZUFsZXJ0UGFyZW50Iq8BQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM5L3Ntb290aG5lc3Muc3luY19zY3JvbGwua2V5X21vYmlsZV9zaXRlc19zbW9vdGgvbWVhbl9pbnB1dF9ldmVudF9sYXRlbmN5L2h0dHBfX193d3cuY25uLmNvbV8yMDEyXzEwXzAzX3BvbGl0aWNzX21pY2hlbGxlLW9iYW1hLWRlYmF0ZV9pbmRleC5odG1sX3JlZgwLEg1TdG9wcGFnZUFsZXJ0GMnHGAw


Bot(s) for this bug's original alert(s):

android-nexus9

Test is disabled only for Nexus 5X: https://cs.chromium.org/chromium/src/tools/perf/benchmarks/smoothness.py?l=269
But runs the test: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus9%20Perf%20%283%29/builds/2514

Result example is here, and it looks returning "NaN" is wrong.
 
smoothness.sync_scroll.key_mobile_sites_smooth smoothness.sync_scroll.key_mobile_sites_smooth
smoothness.sync_scroll.key_mobile_sites_smooth

avg_surface_fps: NaN
first_gesture_scroll_update_latency: NaN
frame_lengths: NaN
frame_time_discrepancy: NaN
frame_times: NaN
input_event_latency_discrepancy: NaN
jank_count: NaN
main_thread_scroll_latency_discrepancy: NaN
max_frame_delay: NaN
mean_frame_time: NaN
mean_input_event_latency: NaN
mean_main_thread_scroll_latency: NaN
mean_pixels_approximated: NaN
mean_pixels_checkerboarded: NaN
percentage_smooth: NaN
queueing_durations: NaN


Device Affinity: 2

Assigned to jdduke@ because this test does not have an OWNER and git blame shows jdduke@ in the test class definition.

Tim could you triage? Thanks.

Example failing trace here:
https://00e9e64bac0976df3ec043794defcd4e433c3f158603f772b4-apidata.googleusercontent.com/download/storage/v1_internal/b/chrome-telemetry-output/o/trace-file-id_2-2016-07-30_15-13-57-55456.html?qk=AD5uMEtGgKzP1AZX_kw2kR0i54uUOVH3QjbQogHTumHklw5Jh01wh7QRmQ95G1wMrdqDnRhclYLPlEPbZ5XWgdLiDQ4Mykr7XrTxridG4ZHzkniZDRwsZEvIXGIp9qn1cC6M6W7vLMQbK_lzlVnahAJb4UQsxL4avbqvCWmb_oL8OnO8Mmrj5ZbSXChByj0M4k9x0g4xL78b1nHXyYLTF_z7ZEqZIZyxsiR2vb-5UiC3BzR7EvGc8EdNvQrPVbH4mVx6vuq_Zsmem0tFNNYAxRopmItuolDVXIgLQqG7ilY9Eog390TKg7_3qJM2oSJ4ws0F0laZc0geZIC8K0fSDgVcxPZoTYTOrCWkLQNPJJSk-tAMUr3DxY91XursSmdwqOixqcaWtcH4iZTzxi1zNPlXKKMSQTGTs9nR-nGQrkDRzz-vV9fY5PIlYi0FjlXm0OJTho4pHE6FSOj9CoyH80sqOl9EMsKNOvRZ8GJ85LHvojDlXlkPmpHTd8Dwdn3nsVdAkyfl6kudsLd2GBJjSOhUqkBW_uNYBFeLvRgUVEnCZk1yLhRaN0GYhyH7xAtwmyiGWt1kSwiKESCL2Mz1cvJbXXK4zz494PqzcMJqATpbqXOvJr0plFFKVf0scD8rbgPEl0Oms6NNygAxRbhBp1lyoqEXtcQi3-b2uWuLsDPcBnfm3IvzmssuU8uVwCWevNX6AkExH_QWrRUE7TCHvxG9KxYwbJddpLWtkPWePsRUr4YtV6eNt0vhOVvjwUSkt7HaJEtKaVkI_0LLhgjBaMy9GhVbMJy9Gx5lDFdIeQwZVFReMHXXLQju7so9j6eFhf6VOJN2Ko4O8I3qfHN-CfvhdXyhS4oBToq8jhmih_KsxbLC-r0Fx8KYC8lh-weJviaMJ-30P839

We aren't seeing any scroll updates.

This looks a bit similar to  issue 627113 .

The best way to follow up on this is to run the test locally with a nexus 9.

Sami/Alex – do we think this benchmark is valuable enough to keep around? It's been providing us a fair bit of pain recently. I'm inclined to think that it is worth keeping around, but I'd be interested to know what you think.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is because the pointer is landing on an input element which prevents the page from scrolling.

We could fix this with a quick hack, but I'd like to think about a more general solution to this problem. Brainstorming in  issue 636378 .

Navid, could you take a look at fixing this specific failure?

To reproduce:
nd content_shell_apk && tools/perf/run_benchmark --browser=android-content-shell smoothness.sync_scroll.key_mobile_sites_smooth --story-filter="michelle"  --output-dir=~/Desktop/missing-gsus/

The output from this is missing gesture scroll updates, so it doesn't produce the input latency smoothness metrics. We want to have this test scroll in a different location, to avoid touching the input element.

A few places to start:
https://cs.chromium.org/chromium/src/tools/perf/page_sets/key_mobile_sites_pages.py?rcl=0&l=56

https://cs.chromium.org/chromium/src/tools/perf/benchmarks/smoothness.py?rcl=0&l=259

https://cs.chromium.org/chromium/src/tools/perf/page_sets/key_mobile_sites_smooth.py?rcl=0&l=143

Look at the custom interaction for GoogleNewsMobile2SmoothPage in that last file. I think we just need a different ScrollElement for the CNN page.

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

commit 5f32fe5b412c4726ba10d053e6958a9186375e4a
Author: nzolghadr <nzolghadr@chromium.org>
Date: Wed Aug 24 22:56:19 2016

Fix page interaction with CnnArticlePage

BUG= 633489 

Review-Url: https://codereview.chromium.org/2262343002
Cr-Commit-Position: refs/heads/master@{#414185}

[modify] https://crrev.com/5f32fe5b412c4726ba10d053e6958a9186375e4a/tools/perf/page_sets/key_mobile_sites_smooth.py

Should this be marked Fixed?

I believe so. I must have forgotten to to that.