I've just reserved Elm for use on the Loop project. The repo is being reset in bug 1006703. Please can we have the following set-up configured: - No nightly builds - No B2G or Android builds - Test runs, the following are the runs required: -- xpcshell, marionette, mochitests (all)

Something like this ? Probably we should disable the nonunified builds, or at least check if they will blindly rebuild every six hours regardless of code change. Not sure about leaving mochitest-e10s enabled either.

Comment on attachment 8419294 [details] List of builders We could certainly disabled the e10s builds, disabling non-unified is fine as well, I don't think we'll need that.

Drops non-unified and mochitest-e10s as well. In mozilla-tests/config.py the location of the loop feels a bit odd, it's a work around to the way we keep appending to the deafault list of suites by gecko version.

Comment on attachment 8419759 [details] [diff] [review] [buildbot-configs] Restrict elm builders Yeah. I think we could refactor things, but I think that would just move the pain points, until we have in-tree scheduling.

Comment on attachment 8419759 [details] [diff] [review] [buildbot-configs] Restrict elm builders https://hg.mozilla.org/build/buildbot-configs/rev/f4bc4cc01ec9

In production

No push since then, but I'll resolve optimistically. Reopen if there are any issues.

Comment on attachment 8419294 [details] List of builders Huh, so I totally meant to set f+ when I commented on this ages ago ;-) and ftr, the changes are working fine.