Closed
Bug 656995
Opened 13 years ago
Closed 13 years ago
run w64 builds from a production master machine
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: armenzg)
References
Details
Attachments
(3 files, 2 obsolete files)
4.05 KB,
patch
|
nthomas
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
3.92 KB,
patch
|
lsblakk
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
1.46 KB,
patch
|
armenzg
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
W64 builds, which are only just barely in production, are currently run from a staging master, but sent into production for testing. This is a sketchy way to leave things. Let's move that master instance onto a production master VM somewhere, and add it (the master) to the slavealloc UI so we don't forget about it.
Comment 2•13 years ago
|
||
Apart from a lack of slaves, is there any reason we can't finish off any config work and run w64 from the main production buildbot masters ? They're defacto supported already.
Assignee | ||
Comment 3•13 years ago
|
||
The only reason is that I have not given to it a high enough priority. I also need to figure out if I want the machine to be doing builds on check-in or not.
Assignee | ||
Updated•13 years ago
|
Priority: P4 → P3
Assignee | ||
Comment 4•13 years ago
|
||
Attachment #539892 -
Flags: review?(nrthomas)
Assignee | ||
Comment 5•13 years ago
|
||
Attachment #539893 -
Flags: review?(nrthomas)
Comment 6•13 years ago
|
||
Comment on attachment 539892 [details] [diff] [review] [configs] enable only win64 slave in production Out of curiosity, will we be mw64-ix-slave01 with the new ref image ?
Attachment #539892 -
Flags: review?(nrthomas) → review+
Comment 7•13 years ago
|
||
*cough* 'scuse me. Out of curiosity, will we be re-imaging mw64-ix-slave01 with the new ref image ?
Comment 8•13 years ago
|
||
Comment on attachment 539893 [details] [diff] [review] [custom] disable xulrunner for win64 The very code you're modifying provides a way to disable xulrunner on win64 without putting (more) platform specific hacks in buildbotcustom.
Attachment #539893 -
Flags: review?(nrthomas) → review-
Assignee | ||
Comment 9•13 years ago
|
||
(In reply to comment #7) > *cough* 'scuse me. > > Out of curiosity, will we be re-imaging mw64-ix-slave01 with the new ref > image ? Yes we will. Even though the tools are pretty much the same.
Assignee | ||
Comment 10•13 years ago
|
||
I could have used 'platforms' key for each branch and have one more for mozilla-central but I believe that adding a hack on a clean area made me uneasy. I believe that my patch isolates the hack and won't be mixed with other people making changes to the code. But let me know if you prefer other way of doing this. I hope we have a bigger pool in 2-3 weeks so we can add it for every branch. I have filed a bug for the xulrunner issue.
Attachment #539892 -
Attachment is obsolete: true
Attachment #541744 -
Flags: review?(nrthomas)
Assignee | ||
Updated•13 years ago
|
Attachment #539893 -
Attachment is obsolete: true
Assignee | ||
Updated•13 years ago
|
Priority: P3 → P2
Comment 11•13 years ago
|
||
Comment on attachment 541744 [details] [diff] [review] add win64 to only mozilla-central Lets hope this really is short lived. Have you looked at win64 debug builds at all ?
Attachment #541744 -
Flags: review?(nrthomas) → review+
Assignee | ||
Comment 12•13 years ago
|
||
(In reply to comment #11) > Comment on attachment 541744 [details] [diff] [review] [review] > add win64 to only mozilla-central > > Lets hope this really is short lived. Have you looked at win64 debug builds > at all ? I will run them again today and see where they are at. I can't recall if I disable them because I wanted to have a higher number of build on check-in for the single slave or if they were red or both.
Assignee | ||
Comment 13•13 years ago
|
||
It seems it times out at make buildsymbols; that could not be good as it might require tool fixes rather than code fixes. I will debug it before we start cloning machines. Thanks nthomas.
Assignee | ||
Comment 14•13 years ago
|
||
Comment on attachment 541744 [details] [diff] [review] add win64 to only mozilla-central Landed on default: http://hg.mozilla.org/build/buildbot-configs/rev/cfd8bb439438 I tried to get leak builds up to speed but for now it won't happen as we have these 2 bugs: bug 669384 and bug 670915.
Attachment #541744 -
Flags: checked-in+
Assignee | ||
Comment 15•13 years ago
|
||
Attachment #545492 -
Flags: review?(lsblakk)
Updated•13 years ago
|
Attachment #545492 -
Flags: review?(lsblakk) → review+
Comment 16•13 years ago
|
||
Attachment #545500 -
Flags: review?(armenzg)
Assignee | ||
Updated•13 years ago
|
Attachment #545500 -
Flags: review?(armenzg) → review+
Assignee | ||
Comment 17•13 years ago
|
||
Comment on attachment 545500 [details] [diff] [review] and now for preproduction too! Checked-in yesterday: http://hg.mozilla.org/build/buildbot-configs/rev/86f223351287
Attachment #545500 -
Flags: checked-in+
Assignee | ||
Comment 18•13 years ago
|
||
Comment on attachment 545492 [details] [diff] [review] add win64 to staging as well Checked-in yesterday: http://hg.mozilla.org/build/buildbot-configs/rev/42b6b4df3c1c
Attachment #545492 -
Flags: checked-in+
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → 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
•