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

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


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

chromium-rel-win7-dual
linux-release

===== 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@403617  809.133  47.8027  18  good
chromium@403618  806.029  28.3076  18  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 625636

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6570
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008061715654640768


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

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

Zhenyao, this was triggered by your CL ab3469f (Update WebGL2 conformance tests) but the bisection did not confirm it.  If you think there's nothing more to this, please close this issue as a "won't fix".

absolutely 0 possibility that my CL caused this.  My CL simply roll in some updates in WebGL 2 conformance test suite.  Not touching any chrome code at all, so 0 impact on chrome perf.