If this is a serious problem, and I can easily believe that it is, have we considered having a default behaviour of cancelling all unfinished Try jobs running for a given user when they push again? Based on how I've seen people use Try over the years, I suspect a significant majority of pushes are updated versions of previous pushes.
For cases where a developer needs to run multiple runs at once, we can add an override in the trychooser syntax. I think that's a corner case, and I don't think it would be a major burden vs. the cost/benefit for everyone else. I think the treeherder path we wouldn't need to auto-cancel, but we would prompt when the user adds jobs from the web interface. -- Mike On Fri, Apr 15, 2016 at 11:47 AM, Ryan VanderMeulen < [email protected]> wrote: > I'm sure most of you have experienced the pain of long backlogs on Try > (Windows in particular). While we'd all love to have larger pools of test > machines (and our Ops people are actively working on improving that!), one > often-overlooked thing people can do to help with the backlog Right Now is > to cancel pending jobs on pushes they no longer need (i.e. newer push to > Try, broken patch, already pushed to inbound, etc). > > Treeherder makes it easy to do this - just hit the little circle with an X > icon on the right hand side adjacent to the "XX% - Y in progress" text > along the top bar of the push. You will be prompted whether you really want > to cancel all jobs on the push. Just hit OK and you're done. > > Killing off unnecessary jobs can have a significant impact on wait times > and backlog, so your consideration is greatly appreciated! > > Thanks, > Ryan > > _______________________________________________ > firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/firefox-dev > > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
