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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgovXSrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgove-sgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4vbWpwoM


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

android-nexus5X
chromium-rel-mac-retina
chromium-rel-win10

===== 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@402362  901.042  31.7826  18  good
chromium@402377  904.943  24.8699  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 624766

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: 1.78%
Score: 0

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


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

| 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

epertoso@, can you follow up on this?

Looking at the graph, it seems like the performances went back to how they were before with this V8 commit: https://chromium.googlesource.com/chromium/src/+/5cda2bdc6c8777e3b9d02c1435dc93397488c5d0.

I couldn't identify a specific CL in the original alert, but by looking at the V8 commit I suspect these alerts were also related to https://bugs.chromium.org/p/chromium/issues/detail?id=624309.

===== 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@402383  944.973  34.3651  18  good
chromium@402401  938.506  22.1118  18  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 624766

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/586
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007427928280724448


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

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