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

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


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

chromium-rel-mac12

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

=== Auto-CCing suspected CL author altimin@chromium.org ===

Hi altimin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Alexander Timin
  Commit : 9ffb4350f06f045c4ae096d97079a654be70b352
  Date   : Sat Oct 07 18:28:54 2017
  Subject: [scheduler] Add missing enum association

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : speedometer
  Metric       : AngularJS-TodoMVC/AngularJS-TodoMVC
  Change       : 9.58% | 402.907833333 -> 441.5245

Revision             Result                  N
chromium@507294      402.908 +- 10.6137      6      good
chromium@507297      411.579 +- 16.1918      6      good
chromium@507299      403.485 +- 5.98727      6      good
chromium@507300      441.525 +- 24.1274      6      bad       <--

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

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

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


For feedback, file a bug with component Speed>Bisection

The patch in question touches only histograms/enums.xml, I do doubt that it is the real cause. Also metric seemed to return to normal, so I'd tempted to say that it is a flake.

Assigning back to the sheriff to confirm.