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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx8mCkggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp4XnsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp4_drAoM


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

android-nexus5X

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

===== 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@435103  9853.63  1227.61  25  good
chromium@435108  9877.14  1464.77  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 671058

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.css
Test Metric: StyleSheetInsert-bootstrap/StyleSheetInsert-bootstrap
Relative Change: 0.24%

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


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

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

=== PERF REGRESSION ===


=== Auto-CCing suspected CL author rob@robwu.nl ===

Hi rob@robwu.nl, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : Remove XSS from chrome://downloads
Author  : rob
Commit description:
  
BUG= 668653 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2526323004
Cr-Commit-Position: refs/heads/master@{#435104}
Commit  : 6d9a7916b48581f72fda060a1210ebef7f89b229
Date    : Tue Nov 29 23:26:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435103  10160.1  1513.43  25  good
chromium@435104  9933.0   792.873  25  bad    <--
chromium@435105  9910.12  781.694  25  bad
chromium@435106  9870.08  976.517  25  bad
chromium@435108  9858.75  1407.19  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 671058

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.css
Test Metric: StyleSheetInsert-bootstrap/StyleSheetInsert-bootstrap
Relative Change: 2.97%

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


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

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

This isn't a real regression, was just noise caused by https://github.com/catapult-project/catapult/issues/3050.