User:Sardisson/Crash Analysis Workflow

From Camino Wiki
Jump to navigation Jump to search

bsmedberg asked ss and I to write up our thoughts on how we use (or would like to use) crash analysis reporting and make them available for the denizens of mozilla.dev.quality and the socorro server engineering team.

Below is where I am working through my thoughts.

Releases

During the Release Candidate stage and for the first while after a release,

  • Get an overview of where the crashes are occurring
  • Check

Development Branches

On a weekly basis, I want to look at the accumulated crash stats for that branch and

  • Quickly see where the top crashes are occurring (crash signatures)
  • See which crashes are "increasing"
  • From the above screen, access crash stacks for each crash signature
  • Possibly "compare" crash signatures to trunk and releases to see if they're occurring there, too
  • Cross-reference with any existing bugs

If there are no existing bugs on a major-seeming crash, attempt to reproduce from urls and comments and file bug(s).

Retrieved from "http://wiki.caminobrowser.org/index.php?title=User:Sardisson/Crash_Analysis_Workflow&oldid=7831"