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

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


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

android-nexus5

It's not obvious to me what happened here. CCing some owners.

Is it still listed as a step on the bot recipes? Are they being run?

These are tests that run on the Perf bots, as opposed to correctness tests. Not sure about their setup.

https://bugs.chromium.org/p/chromium/issues/detail?id=593348

removed cc_perftests from some bots. Maybe simon has some ideas.

If I'm understanding, according to the alert above, the missing data is: schedule_alternate_tasks_bitmap_tile_task_worker_pool/*

The test is setup to run on the nexus 5 (https://code.google.com/p/chromium/codesearch#chromium/src/testing/buildbot/chromium.perf.json&q=perf.json&sq=package:chromium&l=48) and is running: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2776


I'm not really familiar with cc, but digging through git logs a bit, it kind of looks like it was renamed: https://codereview.chromium.org/1910213005/

cc/raster/tile_task_worker_pool_perftest.cc was deleted and cc/raster/raster_buffer_provider_perftest.cc added, so I think the test data is now called schedule_alternate_tasks_bitmap_raster_buffer_provider/*

Thanks for investigation, Prashant -- if the test was renamed, then:

 (1) the list of monitored tests may need to be updated (chromeperf.appspot.com/edit_sheriffs)
 (2) this bug can be closed

Simon, can you check?

Following things have been renamed -

TileTaskWorkerPoolTest -> RasterBufferProviderTest
TileTaskWorkerPoolPerfTests -> RasterBufferProviderPerfTests
TileTaskWorkerPoolPerfTest -> RasterBufferProviderPerfTest

I don't have permission for chromeperf.appspot.com/edit_sheriffs. (Do let me know if there is any other way to modify the list of monitored tests from codebase?)

Spoke to Quinten offline, looks like data is coming in on those tests:  https://chromeperf.appspot.com/report?sid=d9b25b309257798183e9f9f995c1911f3b1344e8382f27388704ccb16706571c so I think we can just close this.