600534 - table view of crashes should also show when in time crashes occurred for each build

Status: RESOLVED WONTFIX

(Socorro :: Webapp, task)

Description

[chris hofmann]

Attachment: snapshot of current table view of crashes

the table view of crashes like in the attachment show some good information about which builds yielded crashes and which did not, but its also valuable to know when these crashes occurred.  Both views of the the data help to determine of the crashes are time based, or build based, and/or which have the most influence on volume.

A view like below helps to show a more even distribution across days in the case of bug 598007.   


date     tl crashes at nsDiskCacheMap::Open.nsILocalFile..
         
            count build, count build, ...

20100916 2     2 3.6.92010082415, 

20100917 12   10 4.0b7pre2010091704, 
	       1 4.0b62010091408, 1 3.0b12007110904, 

20100918 8     7 4.0b7pre2010091704, 
	       1 3.0b12007110904, 

20100919 46   42 4.0b7pre2010091704, 
	       3 4.0b62010091408, 1 3.6.102010091412, 

20100920 79   67 4.0b7pre2010091704, 
	       7 4.0b7pre2010091904, 4 3.0b12007110904, 
	       1 4.0b7pre2010091804, 

20100921 163  67 4.0b7pre2010091704, 
	      60 4.0b7pre2010092004, 31 4.0b7pre2010091904, 
	       3 3.0b12007110904, 1 3.6.92010082415, 
	       1 3.6.102010091412, 

20100922 136  66 4.0b7pre2010091704, 
	      27 4.0b7pre2010092104, 19 3.0b12007110904, 
	       9 4.0b7pre2010092204, 6 4.0b7pre2010091904, 
	       4 3.0b22007121120, 3 4.0b7pre2010091804, 
	       1 4.0b7pre2010092004, 1 3.0.52008120122, 

20100923 87   32 4.0b7pre2010091704, 
	      27 3.0b12007110904, 8 4.0b7pre2010092204, 
	       8 4.0b7pre2010092004, 4 4.0b7pre2010091904, 
	       3 4.0b7pre2010092104, 2 4.0b7pre2010091804, 
	       1 4.0b7pre2010092304, 1 3.6.62010062523, 
	       1 3.6.102010091412, 

20100924 66   34 4.0b7pre2010091704, 
	      15 4.0b7pre2010092404, 6 3.0b12007110904, 
	       5 4.0b7pre2010092004, 3 4.0b7pre2010091904, 
	       2 4.0b7pre2010091804, 1 3.6.102010091412, 

20100925 87   47 4.0b7pre2010091704, 
	      20 4.0b7pre2010092404, 6 3.0b12007110904, 
	       5 4.0b7pre2010092304, 4 4.0b7pre2010092312, 
	       3 3.6.102010091412, 2 3.0.52008120122, 

20100926 85   40 4.0b7pre2010091704, 
	      25 4.0b7pre2010092504, 10 4.0b7pre2010092004, 
	       5 4.0b7pre2010092404, 4 3.0b12007110904, 
	       1 3.6.102010091412, 

20100927 89   51 4.0b7pre2010091704, 
	      12 4.0b7pre2010092204, 9 4.0b7pre2010092604, 
	       9 4.0b7pre2010092312, 4 3.0b12007110904, 
	       3 4.0b7pre2010092404, 1 3.6.102010091412, 

It would also be good to connect some kind of adu data to each of the builds to help calibrate the crash rates by build, but I'm not sure adu data has the precision to do that, and is probably topic for another bug.

Lets just add the daily breakdown to the table view or create another tab for it.

Comment 1

[Wayne Mery (:wsmwk)]

I could make use this today :)

Comment 2

[Laura Thomson :laura]

We now have: 
- date of first occurrence
- crashes by date in table view
- reporting by buildid

Those things together I think address these needs. Let me know if not.