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

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


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

android-nexus7v2

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8960326249290769904

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/web_animations_staggered_chaining.html?N_0316

Revision             Result                   N
chromium@522054      17.3593 +- 0.285496      21      good
chromium@522076      17.3626 +- 0.377054      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=web.animations.staggered.chaining.html.N.0316 smoothness.tough_animation_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8960326249290769904


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15a821c8840000

Re-kicking bisect with a wider range.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15a821c8840000

+dtu, simonhatch: Another bisect with no values. What can we do with these?

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17cd038a840000

I *think* this was the gitiles issue, based on the date and that the new jobs should get further.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/17cd038a840000

No ref build, and bisects in #3 and #10 didn't reproduce the regression. Not much more we can do to dig in.