Using the new |mach try fuzzy| selector will also make it a lot easier to only schedule exactly what you need. To run what the above try syntax uses, do:
$ ./mach try fuzzy !osx 'web-platform <ctrl-a><enter> That will run every task that doesn't contain the string 'osx', and does contain the string 'web-platform'. On Thu, Aug 3, 2017 at 3:51 AM James Graham <ja...@hoppipolla.co.uk> wrote: > On 02/08/17 22:30, Kim Moir wrote: > > You may have noticed that the time to wait for macosx test results on try > > has been very long (>1day) this week. > > > > We have taken the following steps to address this problem > [...] > > That sounds great! Thanks. > > For everyone else: > > It looks like the queues are still pretty long, and I imagine there are > lots of pending jobs people scheduled that aren't really necessary any > more (e.g. because you already found issues with a patch on other > platforms, or landed in spite of the missing results). > > If you have a try push which requested OSX jobs, but you don't need them > now, it would help if you go back and cancel the remaining jobs for that > push from treeherder (look for the grey circle with a cross inside in > the top right of the push to cancel all unfinished jobs, and the similar > icon in the bottom panel for individual jobs). Also if you are making > new try pushes and don't specifically need OSX testing, it's possible to > limit tests to certain platforms with try syntax like (for running tests > on linux64 and linux64-stylo only): > > try: -b do -p all -u web-platform-tests[x64,linux64-stylo] > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
