Closed Bug 592782 Opened 11 years ago Closed 11 years ago

Tracking bug for build and release of Firefox 4.0b6


(Release Engineering :: General, defect, P1)



(Not tracked)



(Reporter: lsblakk, Assigned: catlee)




(3 files, 1 obsolete file)

No description provided.
Depends on: 590953
Assignee: nobody → armenzg
Priority: -- → P2
revised "go to build" date from dev.planning:

" - send to build on Friday, Sept 17"
Assignee: armenzg → lsblakk
Comment on attachment 474975 [details] [diff] [review]
configs for 4.0b6 automation [waiting for changeset confirmation]

>diff --git a/mozilla2/ b/mozilla2/
> relbranchOverride  = ''

You have to set this to reuse a relbranch, r-
Attachment #474975 - Flags: review?(nrthomas) → review-
plugged in changeset 11e16ebb2d38 - waiting for official confirmation of this before landing
Attachment #474975 - Attachment is obsolete: true
Attachment #474978 - Flags: review?(nrthomas)
Attachment #474978 - Flags: review?(nrthomas) → review+
Comment on attachment 474978 [details] [diff] [review]
configs for 4.0b6 automation with relbranch override
Attachment #474978 - Flags: checked-in+
Attachment #474982 - Flags: review?(lsblakk) → review+
Comment on attachment 474982 [details] [diff] [review]
version bumps for mozilla-central to 4.0b7pre/2.0b7pre

@ comment #7.
Attachment #474982 - Flags: checked-in+
Build 1 has a bug with built-in Feedback extension (testpilot): it's still compatible with 4.0b5, not 4.0b6 and doesn't work (checked on Win32). Please fix the Feedback.
Assignee: lsblakk → catlee
Priority: P2 → P1
Attachment #475065 - Flags: review?(bhearsum) → review+
Comment on attachment 475065 [details] [diff] [review]
automation bumps for build 2


with sourceRepoRevision = 633e895d5e84
Attachment #475065 - Flags: checked-in+
Closed: 11 years ago
Resolution: --- → FIXED
I know you'll think I'm crazy, but I can't help it.  The following commit:

changeset:   53771:c14c5fe155da
user:        Nick Thomas <>
date:        Tue Sep 14 16:57:00 2010 +1200
summary:     Bug 592782 - Bump nightly version to 4.0b7pre.  r=lsblakk a=releng
is causing (32-bit/i686) linux firefox to crash on startup.

I've submitted crash reports to prove it:

I get the same crash with my own builds as the ones I download from  My 64-bit linux machine is not affected by this problem.
(I haven't tested the Windows builds.)

I applied (-R) the patch from "hg log -p -r 53771" to today's hg repo
($hg summary
parent: 54194:e36e9e20741f tip)
and the resulting firefox is what I'm using to submit this comment.

Today's build without reverting the patch crashes as before.

I'm stumped.  I hope you're not.
You're not crazy. The version change landed as part of a bundle of other fixes
Have a look in that list for the real culprit.
Maybe not crazy, but definitely confused :)  Just to clarify, the exact patch I applied (-R) is pasted below.  It changes no code whatever, just changes a few text files to reflect a higher version number.

Do the numbers in those text files actually determine what source code gets compiled and/or gets executed at startup?

Thanks for your time and patience.

diff -r 7aab25634114 -r c14c5fe155da browser/config/version.txt
--- a/browser/config/version.txt        Fri Sep 10 17:49:26 2010 +1200
+++ b/browser/config/version.txt        Tue Sep 14 16:57:00 2010 +1200
@@ -1,1 +1,1 @@
diff -r 7aab25634114 -r c14c5fe155da config/milestone.txt
--- a/config/milestone.txt      Fri Sep 10 17:49:26 2010 +1200
+++ b/config/milestone.txt      Tue Sep 14 16:57:00 2010 +1200
@@ -10,4 +10,4 @@
 # hardcoded milestones in the tree from these two files.
diff -r 7aab25634114 -r c14c5fe155da js/src/config/milestone.txt
--- a/js/src/config/milestone.txt       Fri Sep 10 17:49:26 2010 +1200
+++ b/js/src/config/milestone.txt       Tue Sep 14 16:57:00 2010 +1200
@@ -10,4 +10,4 @@
 # hardcoded milestones in the tree from these two files.
Oh hmm, I missed that. If you can reproduce in a new profile then I'd file it against Core::Javascript.
Happily, someone has already fixed it.  Nightlies are no longer crashing.
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.