Looking at this, every single test seems to be failing with "shard #0 expired, not enough capacity"


There also don't seem to be any bots able to run the test, kinda looks like the dimensions changed. This looks like it's set via perf_data_generator.py, should I update that?

Yes that is where it is updated.  You could also remove the OS dimension all together.  Since we target very specific devices with device-id that is a unique identifier for the bot and is the only necessary dimension.

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

commit 56fd063683018627c56f813874e1ba28661e8baa
Author: Simon <simonhatch@chromium.org>
Date: Thu Mar 08 18:14:46 2018

Change dimensions for win high-DPI

They seem to have changed on the bot, changing here to match.

Bug:  819780 ,  818877 
Change-Id: I305892716bcb337df71a1f1e2d0937c0db8541b6
Reviewed-on: https://chromium-review.googlesource.com/953379
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Simon Hatch <simonhatch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541839}
[modify] https://crrev.com/56fd063683018627c56f813874e1ba28661e8baa/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/56fd063683018627c56f813874e1ba28661e8baa/tools/perf/core/perf_data_generator.py