That's a very good point about keeping the treeherder page open eating
resources. I guess I've found that (1) my personal try push page takes
much, much longer to get overloaded than eg the inbound page (or worse,
the *full* try page); and (2) Firefox is so flaky on me for other
reasons that I end up having to restart it fairly often anyway. (And no,
it's not because of that page -- half the time I need to restart, that
tab isn't even loaded.)
Generally speaking, Firefox's stability has not been good for me for 2-3
months. I'd like to file a bug, but I've already used up my quota of
unactionable bugs, and if I dug into all of my idiosyncratic issues I'd
never get any work done. I seem to do things differently, in some
problematic way. I wish I could get more use out of the profiler &
cleopatra, but when I'm having issues it often can't manage to load that
page successfully. Plus, for some reason I am mentally incapable of
getting useful (actionable) data out of that UI (or the necessary data
isn't there? not sure.) PEBKAC, I'm sure.
On 04/16/2016 08:32 PM, Nicholas Nethercote wrote:
I use T-pushes on try a lot, where I build on all platforms (debug and
opt) but run tests only on one platform (debug and opt), usually
Linux64. I.e.: "try: -b do -p all -u none[x64] -t none[x64]".
I think you meant "try: -b do -p all -u all[x64] -t all[x64]".
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
