Closed
Bug 717797
Opened 12 years ago
Closed 8 years ago
Please have a Crash report listing by bug numbers (top crashes by bug)
Categories
(Socorro :: Webapp, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
References
Details
(Whiteboard: [q4])
Please have a Top Crash report listing by bug numbers. looking at the crash signatures, sometimes multiple bugs have the same crash signatures due to skiplist needing to be adjusted. It would also help to see the reverse end from the bug number listings.
Comment 2•12 years ago
|
||
Going to run some summaries from which we can generate this data.
Assignee: nobody → benjamin
Status: NEW → ASSIGNED
Comment 3•12 years ago
|
||
Here's what I've got so far: https://crash-analysis.mozilla.com/bsmedberg/20120827/topcrashbybug-aurora.txt scoobidiver, is this data useful as-is? As it stands since a signature can map to multiple bugs, you can't really rank things #1/#2, but we can still assign percentages-of-total.
Comment 4•12 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #3) > scoobidiver, is this data useful as-is? As it stands since a signature can > map to multiple bugs, you can't really rank things #1/#2, but we can still > assign percentages-of-total. Here are my first thoughts: * Bugs with the same signatures and count should be in the same row. * Give a rank to all bugs except bugs that are already counted higher (e.g. don't rank Bug 779657/Bug 779830). * Show the percentage of total. * Limit it to 300 bugs like top crashers.
Comment 5•11 years ago
|
||
I like it. (In reply to Scoobidiver from comment #4) > (In reply to Benjamin Smedberg [:bsmedberg] from comment #3) > > scoobidiver, is this data useful as-is? As it stands since a signature can > > map to multiple bugs, you can't really rank things #1/#2, but we can still > > assign percentages-of-total. > Here are my first thoughts: > * Bugs with the same signatures and count should be in the same row. > * Give a rank to all bugs except bugs that are already counted higher (e.g. > don't rank Bug 779657/Bug 779830). > * Show the percentage of total. > * Limit it to 300 bugs like top crashers.
Updated•11 years ago
|
Summary: Please have a Crash report listing by bug numbers → Please have a Crash report listing by bug numbers (top crashes by bug)
Updated•11 years ago
|
Assignee: benjamin → sdeckelmann
Whiteboard: [q4]
Comment 6•11 years ago
|
||
Something like this might provide the information we're looking for: SELECT product_version_id, report_count, signature_id, bug_id, sum(report_count) OVER( PARTITION BY signature_id ) from tcbs JOIN signatures USING (signature_id) JOIN bug_associations USING (signature) where report_date = '2013-08-31' group by signature_id, bug_id, report_count, product_version_id order by sum DESC, product_version_id ; I'll play around with this and see if I can present the information the way Scoobidiver asked.
Updated•8 years ago
|
Assignee: sdeckelmann → nobody
Status: ASSIGNED → NEW
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•