Any conclusions out of the discussion here? Try is getting slower as we speak...
I would opt to less disruptive way at first, per what Brian Grinstead said. We don't even have to implement interactive prompt first. If that makes people cancel old Try runs more, great, if not, we could consider other workflow-breaking solutions. I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1266602 for this. On Tue, Apr 19, 2016 at 2:54 AM, William Lachance <wlacha...@mozilla.com> wrote: > On 2016-04-18 2:46 PM, William Lachance wrote: > >> >> Treeherder did trigger a rather large memory leak which got fixed in the >> browser a while back (Dec 2015), so please consider revisiting it if you >> gave up around then: >> ... >> If anyone feels like profiling and submitting patches, we'd welcome the >> help. :) Getting a UI-only development environment going is trivial: >> http://treeherder.readthedocs.org/ui/installation.html#installation >> > > Just realized that this last comment might make it seem like I'm passing > the buck, which wasn't my intention. :) I do have a lot of other things to > do, but if you continue to have problems using treeherder due to memory > leaks or whatever feel free to file a bug against treeherder and needinfo > me; I promise to give it my attention. > > Will > > _______________________________________________ > 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
