On a planet called Veridian III, a decisive battle was fought to prevent a future firing of a rocket into a star that would change gravitational forces and make "the nexus" crash into the planet as well as destroy the planet with a shock wave. Preventing this catastrophy made the crash of the USS Enterprise on the planet controllable as to suffer no human casualties.
In the same spirit, the project I internally dub "Veridian 3" is about dealing with crashes to make the bad ones preventable and other ones more controllable, all through prioritizing Socorro work.
Those areas have been specified in the contract:
- Improving Crash Data Integrity
- Identification and Removal of Duplicate Crash reports
- Improving Search Capabilities
- Improving Classification and Characterization of Crash Reports and Improved Signature Generation
- additional correlation reports to help identifying circumstances around the crash and steps to reproduce
- Improve Trend Reports to identify and alert teams about Explosive bugs
Prioritization Comments From Socorro Users
<wsmwk> KaiRo: second tier needs might be bug 421119, bug 518823, bug 578376, bug 411354. third tier: bug 527304, bug 512910, better workflow for updating skiplist) <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=421119 min, P3, 2.1, nobody, NEW, function for socorro to compare stacks of two or more crash reports <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=518823 enh, --, Future, nobody, NEW, indicate bug's status for bugzilla keyword topcrash <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=578376 nor, --, ---, nobody, NEW, multiple crashes from a single person should have less weight then many crashes from different peopl <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=411354 nor, P1, 2.0, nobody, REOP, Add ability to search by build ID <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=527304 enh, --, ---, nobody, REOP, provide smart analysis ala talkback <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=512910 enh, --, ---, nobody, NEW, Make it easier to analyze crashes that share a signature
https://bugzilla.mozilla.org/show_bug.cgi?id=551669 provide graphs by crash date too Smokey Ardisson (way behind; no bugmail - do not email) <firstname.lastname@example.org> changed: CC| |email@example.com
johnjbarton Of course *all* of my crashes involve Firebug. The number one question I have when I visit crash-stats site is: How many other users who have this crash also running Firebug? If the answer is 95%, then I better spend some time on it because no one else will. If the answer is 5%, I'm having lunch.
Jeff Muizelaar It would be nice if it was possible to get more summary information about a crash. For example: What build ids does this crash all occur with? What operating system versions does this all occur with? etc.
Josh Matthews I, like Jeff, would appreciate summaries of the data available - most recent 10 unique build ids, list of unique OS versions, range of uptimes, etc. I would also be really interested in data about spikes - seeing a graph of the number of crashes for a particular signature over time would be useful to track trends.