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

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


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

chromium-rel-win7-dual

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

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

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

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

Suspected Commit
  Author : Ken Rockot
  Commit : 474df01407e5d38c85364ae4d1709b8d9af16f16
  Date   : Wed Jul 12 13:28:56 2017
  Subject: Mojo C++ Bindings: Lazy Serialization

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile
  Change       : 1.85% | 8.06388888889 -> 8.21333333333

Revision             Result                    N
chromium@485931      8.06389 +- 0.248473       9      good
chromium@485933      8.00917 +- 0.244685       6      good
chromium@485934      7.96667 +- 0.0433974      6      good
chromium@485935      8.24 +- 0.118743          6      bad       <--
chromium@485938      8.24833 +- 0.15308        6      bad
chromium@485945      8.25417 +- 0.221406       6      bad
chromium@485959      8.24833 +- 0.0606905      6      bad
chromium@485987      8.2875 +- 0.154394        6      bad
chromium@486042      8.21333 +- 0.142068       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 service_worker.service_worker_micro_benchmark

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

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


For feedback, file a bug with component Speed>Bisection

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

Hi vabr@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 : Vaclav Brozek
  Commit : fd8b83c8aba9791af6e6116b5db2e0a3d034872c
  Date   : Wed Jul 12 10:15:58 2017
  Subject: Password settings on iOS: use Title Case

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_1_response_50_percentile/concurrent_1_response_50_percentile
  Change       : 4.25% | 1.35166666667 -> 1.40916666667

Revision             Result                    N
chromium@485899      1.35167 +- 0.011547       6      good
chromium@485906      1.35083 +- 0.016457       6      good
chromium@485909      1.35667 +- 0.0387298      9      good
chromium@485911      1.3575 +- 0.0252488       6      good
chromium@485912      1.4375 +- 0.109943        6      bad       <--
chromium@485924      1.47583 +- 0.202289       6      bad
chromium@485949      1.40917 +- 0.0228218      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 service_worker.service_worker_micro_benchmark

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

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


For feedback, file a bug with component Speed>Bisection

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

Hi vabr@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 : Vaclav Brozek
  Commit : fd8b83c8aba9791af6e6116b5db2e0a3d034872c
  Date   : Wed Jul 12 10:15:58 2017
  Subject: Password settings on iOS: use Title Case

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile
  Change       : 14.95% | 7.09666666667 -> 8.1575

Revision             Result                    N
chromium@485899      7.09667 +- 0.100664       6      good
chromium@485906      7.08167 +- 0.092376       6      good
chromium@485909      7.0725 +- 0.190493        6      good
chromium@485911      7.05917 +- 0.0708578      6      good
chromium@485912      7.63556 +- 1.26926        9      bad       <--
chromium@485924      7.6175 +- 0.466838        6      bad
chromium@485949      8.1575 +- 0.791067        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 service_worker.service_worker_micro_benchmark

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

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


For feedback, file a bug with component Speed>Bisection

Bisect results are wrong: that CL only affects iOS.

Also I don't know why the bot reassigned the bug when it already duped to another bug.