610942 - "Versions" column in topcrashers CSV doesn't differentiate between products, has version number collisions

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

The new "Versions" column in the CSV output files doesn't account for multiple products very well; in particular, both Camino and SeaMonkey are releasing 2.0.x releases right now, and all 2.0.x versions ≤ 2.0.5 are ambiguous (presumably they're all current/recent Camino releases rather than older SeaMonkey releases, but it's impossible to know).

Can we annotate every version with the standard Fx, Tb, Cm, Sm prefixes so that the versions make sense?

Alternatively, or in addition, could we make "same product" versions all first/together, or in a separate column from "other product" versions?

I like being able to see at a glance which products/versions also suffer from a given crash I'm seeing in Camino, but at the same time it's less useful if I don't know if a 2.0.x version is my own or SeaMonkey…

Comment 1

[chris hofmann]

are you talking about the .csv files in
http://people.mozilla.com/crash_analysis/20101109/ like 
20101109-pub-crashdata.csv.gz ?

If so, I'm pretty sure those are only Firefox crashes.  Rather than adding a product field we should just create new files for products that want to use the .csv's for analysis.

That also solves the complicated product/version checks that analysis scripts would have to implement to make sure they are looking at the right set of data as you outlined above.

If anyone is intested in looking across products they can just grab all the the .csv's across products.

we could change the file naming conventions to include product names, like dbaron has done with the module and addon analysis files.

Comment 2

[K Lars Lohn [:lars] [:klohn]]

I'm assuming you are talking about something other than the daily dump crashes in csv format.  I believe that cron job is only dumping Firefox crashes, though it can be configured to do others.  Column 6 within that csv is product name while column 7 is the version.

Please clarify where you are getting this csv so that we can make sure we're looking at the same subsystem.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #2)
> Please clarify where you are getting this csv so that we can make sure we're
> looking at the same subsystem.

The URL in the URL field, https://crash-stats.mozilla.com/topcrasher/byversion/Camino/2.0.5?format=csv ;)

Sorry, I thought those were the same CSVs that chofmann was always filing bugs to have things added to, but I guess not. :(

Comment 4

[Ryan Snyder [:ryansnyder] [:rsnyder] [:rysny]]

Okay, I'm seeing this problem as well.  It also appears when you mouseover the number in the number of versions in the Ver column on the topcrashers page:
http://crash-stats.mozilla.com/topcrasher/byversion/Camino/2.0.5

The query in fetchTopcrasherVersions() in the topcrashers model will need to be updated to make this query product specific.

Comment 5

[Wayne Mery (:wsmwk)]

I'd like to see 
Fx: v.r, v.r, v.r  Tb: v.r, v.r, ...

feel free to skip the commas

Comment 6

[Ryan Snyder [:ryansnyder] [:rsnyder] [:rysny]]

Committing.

This will not push to stage until stage is migrated to 1.7.7.

==

Sending        webapp-php/application/controllers/topcrasher.php
Sending        webapp-php/application/models/topcrashers.php
Transmitting file data ..
Committed revision 2830.