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

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


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

android-nexus5X

I wonder if this is the same as https://bugs.chromium.org/p/chromium/issues/detail?id=609482?  If so we can close this.

Kicked off another bisect here:
https://chromeperf.appspot.com/group_report?bug_id=609768

The thread_other_cpu_time_per_frame metric recovered and subsequently regressed.  Maybe we can close this?

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Trying another bisect.

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev    N   Good?
chromium@391457  0.130182  0.0312663  18  good
chromium@391472  0.136058  0.0215369  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 609768

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_other_cpu_time_per_frame/thread_other_cpu_time_per_frame
Relative Change: 5.51%
Score: 0

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


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

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

Perf sheriff ping: reminder to follow up on possible performance issues

@vmiura, the bisect couldn't reproduce this, and the test is pretty noisy. Should we close this?

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/737
Failure reason: the build has failed.
Additional errors:
Either of the initial "good" or "bad" revisions failed to be tested or built.

There have been further regressions and progressions since this was originally filed. WontFix.

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