Closed
Bug 660616
Opened 13 years ago
Closed 13 years ago
Jaegermonkey builds have the wrong update channel
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tim_vdeynde, Assigned: nthomas)
References
()
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
mozilla
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110530 Firefox/6.0a1
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110530 Firefox/6.0a1
I'm on the Jaegermonkey nightly builds and noticed TI got disabled on update. This was not due to errors in TI builds, because downloading the new version worked just fine. After investigation, I noticed in about:buildconfig the update channel is the general nightly one (--enable-update-channel=nightly).
Reproducible: Always
Steps to Reproduce:
Download a Jaegermonkey build (http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-jaegermonkey/) and wait for an update
Actual Results:
The nightly build updates to the general channel
Expected Results:
Its update channel should be Jaegermonkey builds
Assignee | ||
Comment 1•13 years ago
|
||
In the latest linux64 nightly (but affects all platforms):
cp configs/mozilla2/linux64/generic/nightly/mozconfig .mozconfig
The 'generic' should be 'jaegermonkey'.
Blocks: 647328
Status: UNCONFIRMED → NEW
Component: Build Config → Release Engineering
Ever confirmed: true
OS: Linux → All
Product: Firefox → mozilla.org
QA Contact: build.config → release
Hardware: x86_64 → All
Version: unspecified → other
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → nrthomas
Priority: -- → P2
Assignee | ||
Comment 2•13 years ago
|
||
From dump_master.py, the net effect of this is s/generic/jaegermonkey/ on (eg)
C {'command': ['cp', 'configs/mozilla2/linux/generic/nightly/mozconfig', '.mozconfig'], 'description': ['copying', 'mozconfig'], 'descriptionDone': ['copy', 'mozconfig'], 'haltOnFailure': True, 'name': 'cp_mozconfig'} {}
for
Linux jaegermonkey build
Linux jaegermonkey leak test build
Linux jaegermonkey nightly
Linux x86-64 jaegermonkey build
Linux x86-64 jaegermonkey leak test build
Linux x86-64 jaegermonkey nightly
Linux QT jaegermonkey build
OS X 10.5.2 jaegermonkey leak test build
OS X 10.6.2 jaegermonkey build
OS X 10.6.2 jaegermonkey leak test build
OS X 10.6.2 jaegermonkey nightly
WINNT 5.2 jaegermonkey build
WINNT 5.2 jaegermonkey leak test build
WINNT 5.2 jaegermonkey nightly
Adds the missing QT mozconfig too.
The switch to the jaegermonkey configs keeps us on gcc 4.3.3, which bug 658452 will fix.
Attachment #536186 -
Flags: review?(aki)
Updated•13 years ago
|
Attachment #536186 -
Flags: review?(aki) → review+
Assignee | ||
Comment 3•13 years ago
|
||
This will probably go live on Thursday, as bug 557260 has to get in first.
Assignee | ||
Comment 4•13 years ago
|
||
Comment on attachment 536186 [details] [diff] [review]
[buildbot-configs] Override generic mozconfigs
Bummer, need more mozconfigs now that bug 557260 landed.
Attachment #536186 -
Attachment is obsolete: true
Assignee | ||
Comment 5•13 years ago
|
||
This adds some more mozconfig copies.
Attachment #536512 -
Flags: review?(aki)
Updated•13 years ago
|
Attachment #536512 -
Flags: review?(aki) → review+
Assignee | ||
Comment 6•13 years ago
|
||
Comment on attachment 536512 [details] [diff] [review]
[buildbot-configs] Override generic mozconfigs + add some more
http://hg.mozilla.org/build/buildbot-configs/rev/2c1fe424715c
Mostly likely to go into production on Thursday morning, in the regular push window.
Attachment #536512 -
Flags: checked-in+
Assignee | ||
Comment 7•13 years ago
|
||
Got merged to production earlier this morning.
Nightlies from 2011-05-02 will have the correct channel, and will update to later jaegermonkey builds. Earlier nightlies will still update to mozilla-central.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•