Closed Bug 724799 Opened 13 years ago Closed 13 years ago

Fx 10 correlation reports have been frozen since Jan 26

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 723182

People

(Reporter: scoobidiver, Assigned: lonnen)

Details

(Keywords: regression)

Fx 10 correlations reports are copies of the ones from Jan 26th: https://crash-analysis.mozilla.com/crash_analysis/20120126/
Assignee: nobody → chris.lonnen
Target Milestone: --- → 2.4.2
Keywords: regression
mass migration of correlation-report related bugs that won't land today.
Target Milestone: 2.4.2 → 2.4.3
Laura, Lonnen, this sounds grave and it _looks_ like this actually started happening when Socorro 2.4.1 has been deployed. I didn't look into the files but at least the sizes of those files for 10.0 look constant which is strange. We need to look into this ASAP.
Severity: normal → blocker
Target Milestone: 2.4.3 → ---
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #2) > Laura, Lonnen, this sounds grave and it _looks_ like this actually started > happening when Socorro 2.4.1 has been deployed. I didn't look into the files > but at least the sizes of those files for 10.0 look constant which is > strange. > > We need to look into this ASAP. AFAICT nothing has changed on the Socorro side. The scripts in question are not part of the Socorro code base (although we are going to move part of it in for the next release, bug 723182) but are checked into IT's puppet install. The cron job was last changed May 6 2011 and the http://hg.mozilla.org/users/dbaron_mozilla.com/crash-data-tools/ checkout in /data/crash-data-tools/ was last modified Feb 14 2011
rhelmer, I didn't think much had changed recently. Could this be because of a double digit release number?
(In reply to Chris Lonnen :lonnen from comment #4) > Could this be because of a double digit release number? Firefox 11 has no problem but maybe it's caused by the zero in 10.
Bringing dbaron in because it's his script that are coming up with identical output every day.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
I don't see any change. Is it associated to Socorro 2.4.2 or 2.4.3?
Depends on: 727756
(In reply to Scoobidiver from comment #8) > I don't see any change. Is it associated to Socorro 2.4.2 or 2.4.3? Hmm I think I put the wrong bug in the commit message, sorry.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Robert Helmer [:rhelmer] from comment #9) > (In reply to Scoobidiver from comment #8) > > I don't see any change. Is it associated to Socorro 2.4.2 or 2.4.3? > > Hmm I think I put the wrong bug in the commit message, sorry. I don't think it's too terrible that this commit is associated with this bug (it moves this script into the public repo where everyone could see it), but it definitely doesn't have anything that should fix this bug AFAICT.
No longer depends on: 727756
(In reply to Robert Helmer [:rhelmer] from comment #10) > it definitely doesn't have anything that should fix this bug AFAICT. There was no problem generating correlation reports with 10.0.1 in Socorro 2.4.1. So it's no longer a problem.
Severity: blocker → normal
No longer blocks: 718389, 716841
Let's mark it as a dupe of bug 723182.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.