to focus on what we can do in the short term, we should focus on debug tests. I would like to see: marionette-e10s web-platform-tests reftests mochitest-clipboard mochitest-media reftest crashtest jsreftest xpcshell mochitest devtools* If we feel we need to cut jobs out, lets remove the devtools and leave the rest. That should run per commit without getting too backlogged. Possibly we can adjust our small pool of machines to meet these needs, or leave it slightly larger to account for custom try pushes periodically to verify all tests run.

Joel, what's up with this bug? Was this the set intended to run on the 20 yosemite machines configured with taskcluster-worker?

the intention of this bug was to run tests on a regular basis using taskcluster-worker on the pool of 20 loaner machines. This will give us confidence we can run tests with tc-worker on OSX reliably. We switched gears to BBB- I think we have stalled a bit on this. Possibly we can pick it back up this month?

OK, so this is somewhere in http://migration.taskcluster.net/#/details/taskcluster-worker-on-mac, probably http://migration.taskcluster.net/#/item/macosx-worker-deployment-hardware -- so let's make it depend on that one. Thanks!