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

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


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

chromium-rel-win7-gpu-intel

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

This had a recent improvement then regressed back to original performance. Maybe a revert?

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

Hi yusufo@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 : yusufo
  Commit : 0979251b5a413aa37bb82e8d72d75cd7a1c5e106
  Date   : Tue May 09 06:19:50 2017
  Subject: Only build non rlz_utils targets in non android platforms

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : large-table-collapsed-border-change-with-backgrounds/large-table-collapsed-border-change-with-backgrounds
  Change       : 6.42% | 118.96075 -> 126.602583333

Revision             Result                   N
chromium@470178      118.961 +- 1.35028       6      good
chromium@470216      120.244 +- 0.773778      6      good
chromium@470235      119.948 +- 1.37585       6      good
chromium@470245      121.943 +- 1.73545       6      good
chromium@470246      122.709 +- 4.08012       9      good
chromium@470247      126.275 +- 1.69838       6      bad       <--
chromium@470248      124.361 +- 1.02805       6      bad
chromium@470250      124.432 +- 2.28981       6      bad
chromium@470254      126.603 +- 0.951105      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 blink_perf.paint

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

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


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

That seems like a really weird result, although the numbers are consistent. I kicked off another bisect.

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

Suspected Commit
  Author : yusufo
  Commit : 0979251b5a413aa37bb82e8d72d75cd7a1c5e106
  Date   : Tue May 09 06:19:50 2017
  Subject: Only build non rlz_utils targets in non android platforms

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : large-table-collapsed-border-change-with-backgrounds/large-table-collapsed-border-change-with-backgrounds
  Change       : 6.20% | 119.034833333 -> 126.412333333

Revision             Result                   N
chromium@470178      119.035 +- 0.666752      6      good
chromium@470216      120.09 +- 0.487895       6      good
chromium@470235      119.852 +- 0.867338      6      good
chromium@470245      122.15 +- 1.38985        6      good
chromium@470246      122.286 +- 1.3905        6      good
chromium@470247      126.888 +- 2.11491       6      bad       <--
chromium@470248      124.715 +- 1.67692       6      bad
chromium@470250      124.775 +- 2.36464       6      bad
chromium@470254      126.412 +- 0.960785      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 blink_perf.paint

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

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


| 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!

Pretty sure this is actually the same as crbug/721287. The reason bisect doesn't find it is that (due to noise) it is outside the range. Kind of wired it keeps coming back to this CL though :(