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

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


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

linux-release

Something's wrong with the Perf alerting infrastructure. These tests require GPUs to run, and the Linux Release Perf bot deliberately doesn't have a GPU. Here are links to the most recent successful build which demonstrates that all of the tests are skipped:

https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf/builds/486

https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FLinux_Perf%2F486%2F%2B%2Frecipes%2Fsteps%2Fsmoothness.tough_webgl_cases_on__102b__GPU_on_Linux%2F0%2Fstdout#

There must have been a recent change to the Perf dashboard infrastructure. Assigning to Annie to dispatch and/or duplicate.

It looks like this only ran for one build in february: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf/builds/375

I'm not sure how this happened, but since it stopped after the single build, will WontFix.