Closed
Bug 384150
Opened 17 years ago
Closed 17 years ago
Switch to fx-linux-tbox for nightly builds
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: rhelmer)
Details
Attachments
(3 files)
2.54 KB,
patch
|
coop
:
review+
|
Details | Diff | Splinter Review |
1.43 KB,
patch
|
coop
:
review+
|
Details | Diff | Splinter Review |
1022 bytes,
patch
|
Details | Diff | Splinter Review |
We want to switch to fx-linux-tbox for Linux trunk nightly builds
1) switch it to produce the official trunk nightlies and updates
2) turn on perftests for it (again? They went missing recently)
3) turn off trunk builds and perftests for argo-vm (keep this configuration around for a while, in case we change our mind about this whole fx-linux-tbox thing)
Assignee | ||
Updated•17 years ago
|
Assignee: build → rhelmer
Assignee | ||
Comment 1•17 years ago
|
||
Assignee | ||
Comment 2•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Attachment #268134 -
Attachment is patch: true
Assignee | ||
Comment 3•17 years ago
|
||
Comment on attachment 268134 [details] [diff] [review]
make fx-linux-tbox the default nightly for fx/linux/trunk
changes to replace argo-vm with fx-linux-tbox as default linux nightly trunk build
Attachment #268134 -
Flags: review?(preed)
Assignee | ||
Comment 4•17 years ago
|
||
Comment on attachment 268135 [details] [diff] [review]
changes for perf test box
point test box at fx-linux-tbox not argo-vm
Attachment #268135 -
Flags: review?(preed)
Assignee | ||
Comment 5•17 years ago
|
||
Here's the plan for this:
1) disable "Fx-Trunk-Test" on bl-bldlnx02
2) disable "Fx-Trunk-Cairo" on argo-vm
"disable" here means "comment out from multi-config.pl".
Then, these patches can be landed, and bl-bldlnx01/argo-vm and argo-vm will be hidden from the Firefox tree.
Assignee | ||
Updated•17 years ago
|
Attachment #268134 -
Flags: review?(preed) → review?(ccooper)
Assignee | ||
Updated•17 years ago
|
Attachment #268135 -
Flags: review?(preed) → review?(ccooper)
Updated•17 years ago
|
Attachment #268135 -
Flags: review?(ccooper) → review+
Updated•17 years ago
|
Attachment #268134 -
Flags: review?(ccooper) → review+
Assignee | ||
Comment 6•17 years ago
|
||
(In reply to comment #5)
> Here's the plan for this:
>
> 1) disable "Fx-Trunk-Test" on bl-bldlnx02
Sorry, that should read "bl-bldlnx01". This is done.
> 2) disable "Fx-Trunk-Cairo" on argo-vm
Also done.
Landed trunk patch:
Checking in mozconfig;
/cvsroot/mozilla/tools/tinderbox-configs/firefox/linux/mozconfig,v <-- mozconfig
new revision: 1.7; previous revision: 1.6
done
Checking in tinder-config.pl;
/cvsroot/mozilla/tools/tinderbox-configs/firefox/linux/tinder-config.pl,v <-- tinder-config.pl
new revision: 1.7; previous revision: 1.6
done
Landed test_perf branch patch:
Checking in tinder-config.pl;
/cvsroot/mozilla/tools/tinderbox-configs/firefox/linux/tinder-config.pl,v <-- tinder-config.pl
new revision: 1.1.6.13; previous revision: 1.1.6.12
done
Assignee | ||
Comment 7•17 years ago
|
||
Oh, one more thing:
3) update fx-linux-tbox to pull from trunk not feature_gcc411 branch
This is done.
Assignee | ||
Comment 8•17 years ago
|
||
Checking in Tier1_Firefox.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Tier1_Firefox.txt,v <-- Tier1_Firefox.txt
new revision: 1.5; previous revision: 1.4
done
Assignee | ||
Comment 9•17 years ago
|
||
Looks like it's working; I'll close this tomorrow once we know if the nightly goes ok.
Status: NEW → ASSIGNED
Comment 10•17 years ago
|
||
Nit: both --enable-libxul and --enable-places-bookmarks are enabled by default, so they're not needed. I think it'd be best to use as little explicit enabling as possible so we don't run into problems if something gets turned off by default.
Comment 11•17 years ago
|
||
Also, rhelmer switched this box to report to a new graphs server. I think it'd be best to keep sending it to the old one for reference, since it's essentially the same data, just using a different build to get it. Or is my logic flawed here?
Assignee | ||
Comment 12•17 years ago
|
||
(In reply to comment #11)
> Also, rhelmer switched this box to report to a new graphs server. I think it'd
> be best to keep sending it to the old one for reference, since it's essentially
> the same data, just using a different build to get it. Or is my logic flawed
> here?
It's not going to the new graph server, just a new graph on the build-graphs server. Not sure which is the right way to do this; I think what I've done is going to be less surprise.
Assignee | ||
Comment 13•17 years ago
|
||
switched to fx-linux-tbox; let's discuss elsewhere about the name of the graph, etc.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
OS: Mac OS X → Linux
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
•