need hand run of the crash correlation reports for 3.6.14

RESOLVED FIXED

Status

RESOLVED FIXED
8 years ago
2 years ago

People

(Reporter: chofmann, Unassigned)

Tracking

Trunk
x86
macOS

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
there is an emergency stop ship problem holding up the release of 3.6.14

we need to run the dbaron's correlation reports to check for any module or other correlations that might be associated with the the crashes reported in bug 633869

jabba, can you get with aravind to figure out how we might be able to run these by hand as soon as possible.

I believe particular releases only get added after they reach a certain crash volume threashhold, but we need to start running the reports on 3.6.x pre-release candidates so the correlation reports are available to diagnose new crashes like bug 633869
(Reporter)

Updated

8 years ago
Blocks: 633869
(Reporter)

Comment 1

8 years ago
The daily output for the reports we need are like those at

http://people.mozilla.org/crash_analysis/20110213/

and this set of reports:

20110213_Firefox_3.6.13-interesting-addons-with-versions.txt.gz 13-Feb-2011 02:02 1.7M
20110213_Firefox_3.6.13-interesting-addons.txt.gz 13-Feb-2011 02:02 541K
20110213_Firefox_3.6.13-interesting-modules-with-versions.txt.gz 13-Feb-2011 02:02 28M
20110213_Firefox_3.6.13-interesting-modules.txt.gz 13-Feb-2011 02:02 1.1M

except this run needs to be for 3.6.14, not 3.6.13
I think I've got it. I ran the modified script by hand, which pushed some 3.6.14 stuff to http://people.mozilla.org/crash_analysis/20110214/ . Please verify if that is the correct information.
(Reporter)

Comment 3

8 years ago
Thanks!
OK to close this out?
(Reporter)

Comment 5

8 years ago
we could file a new bug to change the algorithm of how 3.6.x releases get added, or just use this bug.

we need to track the 3.6.x shipping releases, and the next release in preview testing.
Sounds like a new bug - thanks!
Component: Socorro → General
Product: Webtools → Socorro
still need this bug?

Comment 8

2 years ago
nah
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.