Closed Bug 640242 Opened 9 years ago Closed 6 years ago
Get dbaron's crashes-by-build list into Socorro
We should work on integrating a number of current "third-party" reports into Socorro proper, with the benefit of better optimized data gathering (using our databases) and nicer UI. One of those is the crashes-by-build list dbaron has in http://dbaron.org/mozilla/crashes-by-build (I guess the real logic is just gathering which builds we have, the links just go to normal socorro serches).
Wait for 1.9 to see if we can do this with ES.
Target Milestone: --- → 1.9
Assignee: nobody → chris.lonnen
Target Milestone: 1.9 → 2.0
Assignee: rhelmer → chris.lonnen
Target Milestone: 2.0 → 2.1
https://crash-stats.mozilla.com/products/Firefox/builds does exist and is basically this report, but it needs some more work to have it for both Aurora and Nightly and to make it less confusing (e.g. having links for all built platforms that in the end go to the same query is suboptimal).
[:KaiRo] Spoke to [:laura] about this bug on Friday and [:lonnen] mentioned that there is another new report that is going to replace this one. Unfortuantely cannot remember which report lonnen refered to but, I am sure he will comment here to add that info. Are you aware of this? I do not want to spend time working on this if it is going to be replaced soon.
I was planning on replacing or integrating the existing 'nightly builds' report with Bug 672606 (https://bugzilla.mozilla.org/show_bug.cgi?id=672606).
(In reply to Chris Lonnen :lonnen from comment #4) > I was planning on replacing or integrating the existing 'nightly builds' > report with Bug 672606 (https://bugzilla.mozilla.org/show_bug.cgi?id=672606). Integrating with that surely makes sense, yes.
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #5) > (In reply to Chris Lonnen :lonnen from comment #4) > > I was planning on replacing or integrating the existing 'nightly builds' > > report with Bug 672606 (https://bugzilla.mozilla.org/show_bug.cgi?id=672606). > > Integrating with that surely makes sense, yes. Where does that leave this bug/report?
(In reply to Schalk Neethling from comment #6) > Where does that leave this bug/report? As a dependency of bug 672606, I guess. Marking as such.
Depends on: 672606
Component: Socorro → General
Product: Webtools → Socorro
Will the nightly crash trends obsolete this?
Target Milestone: 2.4.2 → 2.4.3
Laura, I think I confused my bug titles. Bug 672606 would have covered this bug by providing charts for crashes by build with these tables of links below. I'm unsure of the value of bug 672606, now, though.
Actually, this bug is about something very similar to (or a variant of) https://crash-stats.mozilla.com/products/Firefox/builds - just look at what I linked in comment #0. We'll see how much of the way the nightly crash trends get us, we'll probably need some TCBS-style stuff there as well, but that could just be a live query in the same way as it is in the reports linked here or on /builds.
mass migration of correlation-report related bugs that won't land today.
Brandon: nightly_builds table created on DevDB. Backfilled to Feb. 03.
Kicking these out to 2.6, which roughly matches the next week I'll be working on Socorro. If someone wants to poach these to get them done earlier, that's fine with me.
Target Milestone: 2.5.2 → 2.6
I pretty much think that https://crash-stats.mozilla.com/products/Firefox/builds is actually the same as this. Can we take a look at what the actual differences are and if there's work needed to get this to work for "all" products we have (i.e. all that have FTP scraping for nightly and aurora builds)?
I'm not sure why this ended up assigned to me. Kairo, what are the differences from a user perspective? Also, what's the relative priority here?
Assignee: laura → nobody
Target Milestone: 10 → 13
(In reply to Laura Thomson :laura from comment #15) > I'm not sure why this ended up assigned to me. Kairo, what are the > differences from a user perspective? Also, what's the relative priority > here? Actually, looking at both reports, I'm not sure if we should either just close this bug or keep it around to make links for different OSes work. If the latter, priority is actually pretty low. I guess we did put this up on our priority list just because it wasn't clear that this basically was implemented already. ;-)
Now that MoBeta is out the door, can this be resolved?
(In reply to Chris Lonnen :lonnen from comment #17) > Now that MoBeta is out the door, can this be resolved? MoBeta didn't change anything here, but see comment #16 - if this bug is still valid at all, it's a pretty low-priority improvement.
Can this bug be closed or is there still a need here?
(In reply to Schalk Neethling [:espressive] from comment #19) > Can this bug be closed or is there still a need here? I think it can be closed, we have by-build-date graphs and we can search for specific days.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.