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

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


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

win-zenbook

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@393293  289.76   26.7882  18  good
chromium@393345  279.072  13.9062  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 612476

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: draw-dynamic-webgl-to-hw-accelerated-canvas-2d/draw-dynamic-webgl-to-hw-accelerated-canvas-2d
Relative Change: 2.18%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/171
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012401397293682048


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5904889641697280

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

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@393293  326.101  37.1436  18  good
chromium@393345  319.854  30.9519  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 612476

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: draw-dynamic-webgl-to-hw-accelerated-canvas-2d/draw-dynamic-webgl-to-hw-accelerated-canvas-2d
Relative Change: 4.48%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/240
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008139014581707552


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5818712880316416

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

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

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

I widened to range in a last attempt to reproduce the regression.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@393293  212.77   15.5225  18  good
chromium@393519  216.535  27.1587  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 612476

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: draw-dynamic-webgl-to-hw-accelerated-canvas-2d/draw-dynamic-webgl-to-hw-accelerated-canvas-2d
Relative Change: 12.99%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/272
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007038370026105392


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5830458525351936

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

I think this maybe due to some hardware change. It's sad that the ref build is disable on this benchmark so we can have more confidence about that statement :-(