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

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


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

win-zenbook

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

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

===== 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@407312  176.079  9.62065  18  good
chromium@407353  175.674  8.76471  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 631148

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests media.tough_video_cases_extra
Test Metric: seek/garden2_10s.ogv_seek_warm
Relative Change: 0.91%
Score: 0

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


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

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

===== 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@407300  177.268  8.88892  18  good
chromium@407399  178.755  9.68309  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 631148

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests media.tough_video_cases_extra
Test Metric: seek/video.html?src_garden2_10s.ogv
Relative Change: 1.33%
Score: 0

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


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

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

Not sure what is going on here, bisects are not finding anything. Seems like a change on the bots maybe?

Can't reproduce.