Veridian 3: Difference between revisions
| Line 71: | Line 71: | ||
My suggestion for a delta to watch is an increase in crash frequency of more | My suggestion for a delta to watch is an increase in crash frequency of more | ||
than 50-75% and new crashes in the top 20 overall signatures by version. | than 50-75% and new crashes in the top 20 overall signatures by version. | ||
=== Data From Previous Explosive Crash Bugs === | |||
Used the [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=explos explosive bug query] to find those, trying to pull info out on how those were explosive. | |||
Revision as of 21:18, February 24, 2011
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.
Project areas
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. [tag includes everything on correlations]
- Improve Trend Reports to identify and alert teams about Explosive bugs [tag includes all trend reports]
Bugzilla Tags
Those are used for the classification of Socorro bugs, all starting with "V3", and those will be documented here. In brackets, there are bug counts as of 02/23.
- V3-integrity (32): Affecting Crash Data Integrity, i.e. quality of the original data we have stored
- V3-search (29): Search Capabilities
- V3-classify (46): Classification and Characterization of Crash Reports and Signature Generation
- V3-correlation (33): Correlation reports to help identifying circumstances around the crash and steps to reproduce
- V3-trends (18): Trend Reports, e.g. to identify and alert teams about Explosive bugs
- V3-newreports (18): New reports (requests for generating new reports) - currently in V3-classify
- V3-UI (102): User Interface issues
- V3-nonHTMLoutput (11): Non-HTML/web output (.csv, feeds, etc.)
- V3-notify (14): Notifications (to be) sent out by the Socorro system
- V3-infra (111): Infrastructure and backend issues (note: out of the direct focus of my project, subject to internal planning in the Socorro team)
- V3-config (21): Configuration adaptations (skiplist additions, etc.)
- V3-productization (14): Making Socorro a product that can be deployed and understood by others (documentation, etc.)
- V3-datarequest (7): Data requests (bugs that request data through manual jobs)
Planned but not yet created (or not yet fully done) categories/tags:
- V3-UItweaks (): UI tweaks (probably easy to solve, small UI issues) - subgroup of V3-UI
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
Explosive Crashes
Notes on the work on a set of criteria for finding explosive crash reports - bug 629049 is the tracker bug, bug 629062 is detection. The PRD doc has some surrounding info, but no criteria yet.
Personal Notes
- Sharp increase at certain wall-clock time across versions
- Sharp increase at certain build ID (date?) on single version/series (possibly ignoring everything in version string starting with first letter if the version ends in "pre", to have e.g. 5.0a3pre->5.0b1pre or 4.0b11pre->4.0b12pre not disturb the analysis)
- Ignore (suspected) duplicates
- Frequency weighted by ADU more important than bare count (from something chofmann has said)
User Comments
From https://wiki.mozilla.org/Socorro:PRD_Interviews
damon: * (initial) growth of more than 25 positions in the ranking * upwards change in rank and no related bugzilla id * time since startup < 1 minute * highlight these crashes in red or something
From https://bugzilla.mozilla.org/show_bug.cgi?id=525316
morgamic: My suggestion for a delta to watch is an increase in crash frequency of more than 50-75% and new crashes in the top 20 overall signatures by version.
Data From Previous Explosive Crash Bugs
Used the explosive bug query to find those, trying to pull info out on how those were explosive.