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

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


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

chromium-rel-mac-retina

=== Auto-CCing suspected CL author hiroshige@chromium.org ===

Hi hiroshige@chromium.org, 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 : Remove an ExecutionContextTask subclass in DatabaseTracker
Author  : hiroshige
Commit description:
  
BUG=478194

Review-Url: https://codereview.chromium.org/2099093002
Cr-Commit-Position: refs/heads/master@{#402161}
Commit  : b8d796f8ce8665e7064db8a3ff7b05b45a40c44a
Date    : Mon Jun 27 13:47:05 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@402157  846.443  10.4959  93  good
chromium@402159  850.287  12.4477  93  good
chromium@402160  848.457  11.605   92  good
chromium@402161  842.446  10.5062  93  bad    <--

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 625645

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: React-TodoMVC/React-TodoMVC
Relative Change: 0.94%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1382
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008060884521093360


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

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

Moving this nonessential bug to the next milestone.

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

hiroshige: Ping!

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

That's a really noisy bisect. Trying another one.

Looking at the alert, it looks like it may just have been noise. If the bisect comes back empty-handed we should close this out.

===== 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@402157  845.019  12.526   18  good
chromium@402161  845.641  11.5699  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 625645

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: React-TodoMVC/React-TodoMVC
Relative Change: 0.57%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1437
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006406823843779456


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

| 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 seems to have recovered.  I think we can close this.