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

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


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

chromium-rel-win7-gpu-intel

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435019  770.061  306.05   27  good
chromium@435082  759.594  435.927  27  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 670735

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn
Relative Change: 1.36%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1238
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994369250993687200


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

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435019  771.546  333.565  27  good
chromium@435082  768.234  219.788  27  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 670735

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn
Relative Change: 0.43%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1240
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994183558577165984


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

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435019  761.3    267.688  27  good
chromium@435082  774.339  291.399  27  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 670735

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn
Relative Change: 1.71%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1243
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993985805304468032


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

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

Kicked bisect with a wider range: https://chromeperf.appspot.com/buildbucket_job_status/8993378281543847120

The "good" value should come back somewhere around 400 instead of 760 like the previous bisects.  If not then it's not a Chrome regression and was somewhere in the testing/config.

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434896  448.695  601.764  21  good
chromium@435082  464.027  641.55   21  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 670735

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn
Relative Change: 3.42%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1255
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993378281543847120


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.intl_ko_th_vi
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn

Revision             Result                 N
chromium@435019      518.033 +- 872.52      21      good
chromium@435082      514.66 +- 879.941      21      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 --story-filter=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.