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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=381f0237e745e058ce961eb560dc4acd502b2a619dcdeca2e71f03af63d50530


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

Win 7 Nvidia GPU Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12a61309140000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14ea2f09140000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ea2f09140000

viz: Always request presentation timestamp from clients. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/609997fe600b963b4830c2a713be6839f1856209
queueing_durations: 0.6085 → 0.8795 (+0.271)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

The change is very small, and only two pages are affected. However, the change *improves* for the vast majority of the pages (and are also equally small). So marking as wontfix.

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12a61309140000

unsupported operand type(s) for +: 'float' and 'NoneType'