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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=ec0b0f07ae12414adde489408a0dd4522e763fd44f6082448d522072534039b0


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

Android Nexus6 WebView Perf

speedometer - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15c96daee40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/15c96daee40000

[js weak refs] Add WeakCell.prototype.holdings by marja@chromium.org
https://chromium.googlesource.com/v8/v8/+/8060b60fae4dae5bedadb0de66d25d6ab2a67015
AngularJS-TodoMVC: 8623 → 8537 (-86.78)

[builtins] Port Array.p.join to Torque. by peter.wm.wong@gmail.com
https://chromium.googlesource.com/v8/v8/+/952c097679c5e16ae214595ad3b01381483eab7b
AngularJS-TodoMVC: 8582 → 9053 (+471.2)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

Interesting how status was auto-set to assigned without an owner :)

Other architectures don't show any regression. IMO this isn't actionable.

https://chromeperf.appspot.com/report?sid=43259286269029611d0a8096d15951a2eb46b9eaddc5901ae0a3aacf6184cb16&start_rev=598124&end_rev=602639

 Issue 897067  has been merged into this issue.