I also often have multiple pushes going at the same time. My suggestion to solve this problem is: have a cron job that detects users who have more than N pushes with jobs still going, and send them an email saying "you have a lot of jobs going, here's the list; you might find something you should cancel in there".
Personally, I do keep an eye on my pushes and try to cancel stuff as it becomes unnecessary, but sometimes there might be a few pending jobs on very old pushes that I've neglected to cancel, and will likely not push with that bug number anymore. An email reminder that lists those old pushes would make me realize I can cancel them. kats On Fri, Apr 15, 2016 at 4:02 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 4/15/16 1:09 PM, Tim Guan-tin Chien wrote: >> >> I wonder if there is any use cases to do multiple Try pushes of different >> changesets but with the same bug number. > > > A significant fraction of my try pushes are like this, actually. Typically > this happens when I do a try push of a multi-changeset queue for a bug, get > some mysterious failures, then do several pushes of more and more of the > queue in an attempt to narrow down which changeset is causing the failures. > >> Should we automatically cancel the old ones when there is a new one? > > > If we set this up, I would probably just add whatever the "do not cancel" > override is to my try syntax for everything, to avoid the inevitable > footguns. Unless there were a way to uncancel. > > -Boris > > > _______________________________________________ > 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
