> For tracking top crashes in trunk nightly builds, I've set up:
> which contains links to the top crashes in each nightly build. (I'd
> previously been constructing such queries by hand.)
> This is useful if you want to:
> * see if a patch introduced new top crashes or fixed existing ones
> * help file bugs on the top crashes in current nightlies
This is great work, and I'd like to see this integrated into something like the dev-tree-mgmt-type notifications where if there's evidence of a new crash or spike associated with particular check-ins we're notified. I know it's hard, and there may be false positives. Still, it might help us keep our crashes in check.
Who wants to volunteer to help make that happen? :)
Excellent job, David!
> L. David Baron http://dbaron.org/
> Mozilla Corporation http://www.mozilla.com/
> dev-planning mailing list
Looking per-nightly catches *all* crashes (not just topcrashes), and
can be valuable for that reason.
Where can I grab the Build IDs that we're using to populate dbaron's
page? Are we just fetching those out of the txt files on the FTP
site, or is there a better place to grab those?
> I'm just grabbing the text files from FTP (and then caching them).
> I put the script I used to generate the page at
> I'd note that we currently (as of when I checked a few days ago)
> only seem to publish the .txt files for mozilla-central and not for
> release branches.
I just landed bug 474610 on 1.9.2 and 1.9.1 this morning. Also, I have a
Python script that does basically the same thing (but stores the results in
a sqlite db) here:
I'm just grabbing the text files from FTP (and then caching them).
I put the script I used to generate the page at
I'd note that we currently (as of when I checked a few days ago)
only seem to publish the .txt files for mozilla-central and not for
The links for the crashes for nightly builds are now available in
Crash Stats at:
Let me know if you have any feedback for this page... Thanks David
and Ted for the pointers for the build info files!