Thank you for the work you put in making this happen! I for one certainly appreciate the results - stack symbolication used to be pretty dodgy for me but now it seems fast and reliable!
On Tue, Apr 14, 2020 at 10:22 PM Nicholas Nethercote <n.netherc...@gmail.com> wrote: > > On Fri, 6 Mar 2020 at 09:52, Nicholas Nethercote <n.netherc...@gmail.com> > wrote: >> >> >> I have written a new stack-fixing tool, called `fix-stacks`, which >> symbolizes stack traces produced by Firefox. >> >> [...] >> >> There is more work to be done. Soon, I plan to: >> >> * use `fix-stacks` on test outputs (in `utils.py` and `automation.py.in`); >> >> * re-enable stack fixing on Mac test runs on local builds, which is >> currently disabled because it is so slow; >> >> * add breakpad symbol support to `fix-stacks`; >> >> * remove the old scripts. > > > I have done these four things now. There has been a long tail of issues to > work through relating to test output on automation, and there may still be > problems with obscure build or test jobs or intermittent failures. If you see > any problems where `fix-stacks` is mentioned, please let me know. > > For those of you who are interested in a detailed description of this work, > please take a look at > https://blog.mozilla.org/nnethercote/2020/04/15/better-stack-fixing-for-firefox/. > > Nick > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
