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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggOi3tgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggPSIrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_4HbsAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7eCvwsM


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_input_event_latency/mean_input_event_latency

Revision             Result                  N
chromium@441458      2.85044 +- 36.8896      180      good
chromium@441469      3.14313 +- 52.8348      180      good
chromium@441475      3.13894 +- 52.2054      179      unknown
chromium@441480      7.34712 +- 101.51       180      bad
chromium@441501      7.23471 +- 100.659      180      bad
chromium@441543      7.00494 +- 96.0882      179      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests scheduler.tough_scheduling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990906218164247648

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5881320447672320


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

+simonhatch, dtu: seems like for the bisect in #3 the unknown revision should have been classified as good?

Yeah looks like it should have, it got really close, p 0.0237. We have a bug out to potentially try averaging the values for summary results like this (as the dashboard does), instead of just using the raw data, I'll block on that.

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : dtapuska
  Commit : 5494d50ab65532c64a28e91e23b0a722ebbfe8ed
  Date   : Wed Jan 04 22:02:35 2017
  Subject: Remove the requirement to only rAF align non-blocking touch moves.

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_input_event_latency/mean_input_event_latency
  Change       : 142.88% | 2.82527854406 -> 6.86191111111

Revision             Result                   N
chromium@441410      2.82528 +- 0.802414      6      good
chromium@441477      2.74863 +- 0.477842      6      good
chromium@441478      7.14943 +- 0.459615      6      bad       <--
chromium@441479      7.17247 +- 0.750156      6      bad
chromium@441480      7.14413 +- 1.22329       6      bad
chromium@441482      7.24278 +- 0.803397      6      bad
chromium@441486      7.31022 +- 1.42881       6      bad
chromium@441494      6.89678 +- 0.724246      6      bad
chromium@441510      7.53469 +- 1.29243       6      bad
chromium@441543      6.86191 +- 0.942304      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests scheduler.tough_scheduling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990647830275445488

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5284402268995584


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!