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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgztbOrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgroz3qQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjpuV8wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjr-fsQkM


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

android-nexus5
android-nexus7v2

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

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

===== 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@412365  584.156  28.1111  14  good
chromium@412405  592.575  15.453   11  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 638681

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: time_to_play/video.html?src_crowd1080_vp9.webm_canvas_true
Relative Change: 1.01%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4008
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004055860066310832


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

| 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@412359  588.446  18.4548  11  good
chromium@412405  594.467  18.0914  11  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 638681

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: time_to_play/video.html?src_crowd1080_vp9.webm_canvas_true
Relative Change: 0.38%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4010
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004051545915605856


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

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

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

Started a new bisect with bigger range on the tail end. "Bad" mean value should be ~900.

===== 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@412308  581.934  24.5556  12  good
chromium@412467  601.697  37.4302  9   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 638681

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: time_to_play/video.html?src_crowd1080_vp9.webm_canvas_true
Relative Change: 2.11%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4013
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003960133327786576


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

| 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 not reproducing the graph's results. "Bad" should be ~800 for the chosen revision. Followed a bug for "bad bisect". Standing by for results. 

Graphs are all still recovered and bisect not able to repro the bump. Closing.