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

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


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

android-nexus5

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@429282  1712.96  36.4295  12  good
chromium@429285  1774.55  31.6436  8   bad
chromium@429288  1758.07  27.818   8   bad
chromium@429294  1749.88  30.9118  12  bad
chromium@429305  1777.47  36.3124  8   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 661923

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_es_fr_pt-BR
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.ebay.es_sch_i.html?_sacat_382__trkparms_clkid%3D6548971389060485883__qi_RTM1381637
Relative Change: 3.54%
Score: 0

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


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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1638
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

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


===== SUSPECTED CL(s) =====
Subject : Add crash keys to TaskQueueManager::ProcessTaskFromWorkQueue
Author  : alexclarke
Commit description:
  
We suspect a bad task closure is getting posted and would like to
add crash keys to aid diagnosis.

BUG=660427

Review-Url: https://codereview.chromium.org/2464853002
Cr-Commit-Position: refs/heads/master@{#429285}
Commit  : c08c078b27b353f4ab8de7deccfb862270b1ff2a
Date    : Wed Nov 02 15:49:06 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@429282  1688.94  23.4189  5  good
chromium@429284  1688.98  16.6125  5  good
chromium@429285  1777.19  33.7523  5  bad    <--
chromium@429288  1764.26  31.442   5  bad
chromium@429294  1754.98  19.668   5  bad
chromium@429305  1767.71  21.1859  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 661923

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.ebay.es.sch.i.html..sacat.382..trkparms.clkid.3D6548971389060485883..qi.RTM1381637 page_cycler_v2.intl_es_fr_pt-BR
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.ebay.es_sch_i.html?_sacat_382__trkparms_clkid%3D6548971389060485883__qi_RTM1381637
Relative Change: 4.66%
Score: 99.8

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___msn.co.il_


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 --story-filter='http...msn\.co\.il.' page_cycler_v2.intl_ar_fa_he

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

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


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