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

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


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

android-nexus6

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12b05db9440000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12b05db9440000

[scheduler] Use WorkerSchedulerProxy in DedicatedWorkerThread. by altimin@chromium.org
https://chromium.googlesource.com/chromium/src/+/053b619cf7ac1dd0ed6504e6e65da0e45d0a9d4e

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

That's rather strange. Looking.

 Issue 822813  has been merged into this issue.

 Issue 823348  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/826afc1b01683f467bdaf535e970c084a8d73bf3

commit 826afc1b01683f467bdaf535e970c084a8d73bf3
Author: Alexander Timin <altimin@chromium.org>
Date: Mon Mar 19 19:22:59 2018

Fix compositor thread name

Some benchmarks depend on fixed compositor thread name. Revert the name
back to the old one for compatibility.

TBR=haraken@chromium.org
BUG= 823315 

Change-Id: I07c324016280c33b240fe5f32e5c560ddd9250db
Reviewed-on: https://chromium-review.googlesource.com/969042
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Hector Dearman <hjd@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hector Dearman <hjd@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544110}
[modify] https://crrev.com/826afc1b01683f467bdaf535e970c084a8d73bf3/third_party/WebKit/Source/platform/WebThreadType.cpp

 Issue 823352  has been merged into this issue.

The fix has landed, bots should start feeling better now.

Can confirm that the bots feel better now, when I panicked seeing ~1500 alerts from them saying the have non-zero values now :p