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

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


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

chromium-rel-win7-x64-dual

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

This looks like it's a new test as there doesn't seem to be data for this configuration before. Can you confirm and close if so, or advise next steps otherwise. Thanks.

The test isn't new.  The group report seems busted (+sullivan).

Looking at the reports here it looks like a big regressi: https://chromeperf.appspot.com/report?sid=30dbc087d9c87aa58d10ef498b4d661526aadced6f22f6067385e806d88d4147

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

There is no data for this test between 2016-07-14 and 2016-08-20.  Does anyone know what happened in this time?

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@405407  16.6864  0.0502979  5  good
chromium@413335  103.162  33.458     5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 639764

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/http___games.yahoo.com
Relative Change: 518.24%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1431
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003597581109587840


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@405407  16.6864  0.0502979  5  good
chromium@413335  103.162  33.458     5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 639764

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/http___games.yahoo.com
Relative Change: 518.24%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1431
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003597581109587840


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@405407  16.6991  0.0655015  5  good
chromium@413335  103.322  23.8607    5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 639764

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: frame_times/http___games.yahoo.com
Relative Change: 518.72%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1438
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003597581109587840


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

| 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'm not sure why the bisects were failing or we had a data stoppage right before the regression, but both frame_time and percentage_smooth have recovered: https://chromeperf.appspot.com/group_report?bug_id=639764

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/http___games.yahoo.com

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/12c7998901fcdb7d43284f4621ca95b859fc56e3..3ab8e7edb730b85448fa8a58e19a02b6836000a1


Revision             Result                    N
chromium@405407      16.6991 +- 0.0655015      5      good
chromium@413335      103.322 +- 23.8607        5      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...games.yahoo.com smoothness.top_25_smooth

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

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


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