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

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


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

android-nexus5X

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

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

===== 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@432945  4328.47  3012.78  27  good
chromium@432982  4350.08  2637.33  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 669184

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken
Test Metric: Total/Total
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/916
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994716463995682720


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

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

The metric's results are bimodal. I'm not exactly sure if this benchmark should be doing that. Do you have any thoughts on what could be going wrong?

I have no idea what's going on with this perfbot, but the range doesn't even contain a V8 commit, and Kraken is a JavaScript-only benchmark, so it doesn't look like this is actually a problem with V8. Closing as WontFix from our side, dunno if you want to put infra people to look into this.

=== Auto-CCing suspected CL author jbriance@cisco.com ===

Hi jbriance@cisco.com, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : cc: Cleanup class/struct forward declarations
Author  : jbriance
Commit description:
  
Remove useless class and struct forward declarations, and add
missing ones in cc header files.

BUG= 662195 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2503283002
Cr-Commit-Position: refs/heads/master@{#432964}
Commit  : 58f287687a11f1b9f35371aa708e8b93269b3974
Date    : Thu Nov 17 21:38:05 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432161  3764.28  48.1599  12  good
chromium@432572  3745.2   35.798   5   good
chromium@432778  3764.16  11.5876  5   good
chromium@432880  3758.64  17.2642  5   good
chromium@432931  3762.35  20.4475  8   good
chromium@432957  3762.09  62.0001  18  good
chromium@432963  5981.94  16823.8  18  good
chromium@432964  14528.9  599.091  5   bad      <--
chromium@432965  14121.8  980.175  5   bad
chromium@432966  7660.85  26088.1  27  unknown
chromium@432968  7247.07  20757.4  18  bad
chromium@432969  3773.67  94.8946  27  unknown
chromium@432970  3775.79  91.9003  27  unknown
chromium@432971  3779.33  128.088  27  unknown
chromium@432982  3776.89  50.1339  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 669184

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken
Test Metric: Total/Total
Relative Change: 0.42%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/917
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994716443825863616


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

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

Hi,

To be honest, I don't think that my CL could be related to any perf regression (it should be only code cleaning).
Please let me know if you need an action from me,

Julien

Keeping with comment #6 as this regression is bimodal, so not sure what's going on - it could be infrastructure.