Veridian 3: Difference between revisions

From KaiRoWiki
Jump to navigation Jump to search
No edit summary
 
(72 intermediate revisions by the same user not shown)
Line 11: Line 11:
* Improving Search Capabilities
* Improving Search Capabilities
* Improving Classification and Characterization of Crash Reports and Improved Signature Generation
* 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]
* 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 [tag includes all trend reports]
* Improve Trend Reports to identify and alert teams about Explosive bugs


== Bugzilla Tags ==
== Bugzilla Tags ==


Those are used for the classification of Socorro bugs, all starting with "V3", and those will be documented here.
Moved to https://wiki.mozilla.org/CrashKill/Plan/BugLists


* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-todo V3-todo]''': Bugs that still need triage/classification
== Prioritization Comments From Socorro Users ==
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-integrity V3-integrity]''': Affecting Crash Data Integrity, i.e. quality of the original data we have stored
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-search V3-search]''': Search Capabilities
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-classify V3-classify]''': Classification and Characterization of Crash Reports and Signature Generation
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-correlation V3-correlation]''': Correlation reports to help identifying circumstances around the crash and steps to reproduce
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-trends V3-trends]''': Trend Reports, e.g. to identify and alert teams about Explosive bugs
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-infra V3-infra]''': Infrastructure and backend issues
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-UI V3-UI]''': User Interface issues
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-notify V3-notify]''': Notifications (to be) sent out by the Socorro system
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-config V3-config]''': Configuration adaptations (skiplist additions, etc.)
* '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=V3-productization V3-productization]''': Configuration adaptations (skiplist additions, etc.)


== Comments From Socorro Users ==
Moved to https://wiki.mozilla.org/CrashKill/Plan/Priorities


<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)
== Explosive Crashes ==
<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
Moved to https://wiki.mozilla.org/CrashKill/Plan/Explosive
<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
== Reports ==
<firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=527304 enh, --, ---, nobody, REOP, provide smart analysis ala talkback
 
Moved to https://wiki.mozilla.org/CrashKill/Plan#External_Reports

Latest revision as of 18:20, March 16, 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
  • Improve Trend Reports to identify and alert teams about Explosive bugs

Bugzilla Tags

Moved to https://wiki.mozilla.org/CrashKill/Plan/BugLists

Prioritization Comments From Socorro Users

Moved to https://wiki.mozilla.org/CrashKill/Plan/Priorities

Explosive Crashes

Moved to https://wiki.mozilla.org/CrashKill/Plan/Explosive

Reports

Moved to https://wiki.mozilla.org/CrashKill/Plan#External_Reports

Retrieved from "https://wiki.kairo.at/index.php?title=Veridian_3&oldid=208"