re #82: you set up the scheduler entry in https://chromium.googlesource.com/angle/angle/+log/infra/config/luci-scheduler.cfg

re why it shares the win builder's slave: the dimensions we're setting for angle in cr-buildbucket.cfg only include the pool and the os, not the builder name; doing so apparently requires adding auto_builder_dimension: YES (e.g. https://chromium.googlesource.com/chromium/src/+/master/infra/config/global/cr-buildbucket.cfg#399)

Are the `dimensions: "builder:win-msvc"` lines in https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/bots.cfg#172 unused atm then? I.e. can I remove them for the try bot_groups?

Would I be right in thinking that setting the dimension for the builder would mean faster re-compiles, because the same builder wouldn't be trying to build both MSVC and Clang?

Right now, there's just one win slave for the main waterfall. If you got a second slave assigned to the main waterfall and set the dimensions differently, then yes, win/msvc and win/clang would each have their dedicated slave and they could build concurrently. But if you have just one slave and set the dimension, then the win/msvc bot will cycle twice as fast but no slave would be around for doing the win/clang builds.

OK. I'll see if I can handle this as part of  issue 833999 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/958de8e9747692937531b48033eedcadcaa807a5

commit 958de8e9747692937531b48033eedcadcaa807a5
Author: Jamie Madill <jmadill@chromium.org>
Date: Fri May 04 15:04:19 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/3a1ee730381eca88ea247ac37b455b65ca491cf4

commit 3a1ee730381eca88ea247ac37b455b65ca491cf4
Author: Jamie Madill <jmadill@chromium.org>
Date: Fri May 04 17:39:51 2018