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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgioXh8AsM


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

chromium-rel-win10

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

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations


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/8980153539712753472

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations


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/8980153531766844928

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: e27ff10e692d0cf3d43e7e2a1c8190cbb62cdbb2
  bad_revision : 1ffa169670c2c736d6f1afd38582a4687a5c1e38

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations

Revision             Result                       N
chromium@469195      0.094038 +- 0.00439084       14      good
chromium@469218      0.0943016 +- 0.00350246      14      good
chromium@469224      0.0942086 +- 0.0052106       14      good
chromium@469227      0.0955102 +- 0.0021382       9       bad
chromium@469229      0.0959957 +- 0.00273691      9       bad
chromium@469241      0.0953583 +- 0.00514839      14      bad
chromium@469287      0.0959095 +- 0.00291287      9       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/8980148798050324896

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


| 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 Speed>Bisection.  Thank you!

=== 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: winx64_10_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : queueing_durations/queueing_durations

Revision             Result                       N
chromium@469195      0.094211 +- 0.00478821       21      good
chromium@469241      0.0946859 +- 0.00591829      21      unknown
chromium@469287      0.0951948 +- 0.00569044      21      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/8980061991184755392

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


| 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 Speed>Bisection.  Thank you!

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.