Closed
Bug 519072
Opened 15 years ago
Closed 15 years ago
Setup 10 new linux64 buildslaves with buildbot
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: mozilla)
References
Details
Attachments
(1 file)
1.85 KB,
patch
|
nthomas
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
Per discussion with Shaver Friday afternoon, he wants to start having linux64 build coverage, particularly for JIT work, as quickly as possible.
As we dont have a linux64 refimage yet, we'll spin up an initial 10 clones of the existing moz2-linux64-slave01 VM (with unverified contents), move these into staging, and then production. We might need more depending on what branches are being covered.
This small set of clones is for builds only; priorities around figuring out unittests/talos on linux64 continue, but at this time, they dont exist anywhere afaict.
Note: Until we get a clear refimage setup for linux64, we cannot support linux64 for releases, as we cant guarantee binary compat. However, hopefully, this will help until we create a real, documented, ref image. Once we have a linux64 refimage, we will delete and recreate moz2-linux64-slave03...12. Doing things in this sequence is extra work, but at least this way Shaver gets the linux64 builds he urgently needs in next few days.
Shaver: please confirm which branches you want linux64 builds on for now, and we can create more if these 10 VMs are not enough.
Reporter | ||
Comment 1•15 years ago
|
||
(In reply to comment #1)
> Shaver: please confirm which branches you want linux64 builds on for now, and
> we can create more if these 10 VMs are not enough.
For background, see some earlier suggestions in bug#464027, bug#515457.
Comment 2•15 years ago
|
||
in order of priority:
- mozilla-central
- tracemonkey
- mozilla-1.9.2
thanks!
Reporter | ||
Updated•15 years ago
|
Blocks: support-L64
Comment 3•15 years ago
|
||
joduinn - do we have an owner/priority for this?
Reporter | ||
Comment 4•15 years ago
|
||
(In reply to comment #3)
> joduinn - do we have an owner/priority for this?
shaver wanted these up fairly quickly. As soon as we get the VMs, we should make the slaves run in staging asap. While we wait, I'll assign this bug to myself to get it out of triage queue.
Assignee: nobody → joduinn
Reporter | ||
Comment 5•15 years ago
|
||
(In reply to comment #4)
> (In reply to comment #3)
> > joduinn - do we have an owner/priority for this?
>
> shaver wanted these up fairly quickly. As soon as we get the VMs, we should
> make the slaves run in staging asap. While we wait, I'll assign this bug to
> myself to get it out of triage queue.
Putting this back into the pool now that the VMs are available.
Reporter | ||
Updated•15 years ago
|
Assignee: joduinn → nobody
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 6•15 years ago
|
||
Attachment #409267 -
Flags: review?(nthomas)
Updated•15 years ago
|
Attachment #409267 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 7•15 years ago
|
||
Comment on attachment 409267 [details] [diff] [review]
add moz2-linux64-slave03 through 12
http://hg.mozilla.org/build/buildbot-configs/rev/8aa52d47ce27
Attachment #409267 -
Flags: checked-in+
Assignee | ||
Comment 8•15 years ago
|
||
moz2-linux64-slave03 through 08 on production-master; moz2-linux64-slave09 through 12 on production-master02.
Status: NEW → RESOLVED
Closed: 15 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
•