Closed
Bug 458414
Opened 16 years ago
Closed 16 years ago
Add new slaves to pool
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: joduinn)
References
Details
Attachments
(2 files, 3 obsolete files)
(deleted),
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
bhearsum
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
The current pool of slaves were not able to keep up with all the jobs submitted in the rush to FF3.1b1.
Adding extra slaves to the pool, to help speed up turnaround time for developers.
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → joduinn
Assignee | ||
Updated•16 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•16 years ago
|
||
Doing post-setup steps on new win32 slaves.
Assignee | ||
Comment 2•16 years ago
|
||
Attachment #341663 -
Flags: review?(bhearsum)
Assignee | ||
Comment 3•16 years ago
|
||
redoing, previous patch didnt include the new linux slaves by accident.
Attachment #341663 -
Attachment is obsolete: true
Attachment #341664 -
Flags: review?(bhearsum)
Attachment #341663 -
Flags: review?(bhearsum)
Comment 4•16 years ago
|
||
Comment on attachment 341664 [details] [diff] [review]
add *all* extra slaves to the pool
The linux slaves should get added to mobile_master.py.
You missed tracemonkey altogether.
Attachment #341664 -
Flags: review?(bhearsum) → review-
Assignee | ||
Comment 5•16 years ago
|
||
1) adds linux and win32 slaves to tracemonkey builders
2) adds linux slaves to mobile builders
Attachment #341664 -
Attachment is obsolete: true
Attachment #341667 -
Flags: review?(bhearsum)
Comment 6•16 years ago
|
||
Comment on attachment 341667 [details] [diff] [review]
[checked in] add extra slaves to the pool (v3)
As per the e-mail I sent yesterday please make sure you reconfig the master like this:
vim /tools/buildbotcustom/buildbotcustom/process/factory.py
# uncomment the SetProperty import
cd /builds/buildbot
PYTHONPATH=/tools/buildbot-079:$PYTHONPATH buildbot stop moz2-master
PYTHONPATH=/tools/bulidbot-079:$PYTHONPATH buildbot start moz2-master
vim /tools/buildbotcustom/buildbotcustom/process/factory.py
# recomment the SetProperty import
(Yeah, this is far below ideal - will be fixed next week.)
Attachment #341667 -
Flags: review?(bhearsum) → review+
Comment 7•16 years ago
|
||
(In reply to comment #6)
> (From update of attachment 341667 [details] [diff] [review])
> As per the e-mail I sent yesterday please make sure you reconfig the master
> like this:
> vim /tools/buildbotcustom/buildbotcustom/process/factory.py
> # uncomment the SetProperty import
> cd /builds/buildbot
> PYTHONPATH=/tools/buildbot-079:$PYTHONPATH buildbot stop moz2-master
> PYTHONPATH=/tools/bulidbot-079:$PYTHONPATH buildbot start moz2-master
> vim /tools/buildbotcustom/buildbotcustom/process/factory.py
> # recomment the SetProperty import
>
> (Yeah, this is far below ideal - will be fixed next week.)
Sorry, cut-and-paste-o, ignore that, do this:
vim /tools/buildbotcustom/buildbotcustom/process/factory.py
# uncomment the SetProperty import
cd /builds/buildbot
PYTHONPATH=/tools/buildbot-079:$PYTHONPATH buildbot reconfig moz2-master
vim /tools/buildbotcustom/buildbotcustom/process/factory.py
# recomment the SetProperty import
Assignee | ||
Comment 8•16 years ago
|
||
I've fixed some omissions in the win32 slave setup docs at:
https://wiki.mozilla.org/ReferencePlatforms/Win32#Setup_extra_disk
At this point, the new slave is recognized by staging-master, and can be given jobs to process, but the slave immediately fails out the job with:
exceptions.RuntimeError: Couldn't find executable for 'hg'
Manually logging into the slave, I get:
$ which hg
which: hg: unknown command
...even though I can see /d/mercurial/hg.exe. By contrast when I login to one of the pre-existing slaves, I get:
$ which hg
/d/mercurial/hg.exe
Still working on it.
Comment 9•16 years ago
|
||
Comment on attachment 341667 [details] [diff] [review]
[checked in] add extra slaves to the pool (v3)
changeset: 399:039d7bf5b671
Attachment #341667 -
Attachment description: add extra slaves to the pool (v3) → [checked in] add extra slaves to the pool (v3)
Assignee | ||
Comment 10•16 years ago
|
||
(In reply to comment #8)
> I've fixed some omissions in the win32 slave setup docs at:
> https://wiki.mozilla.org/ReferencePlatforms/Win32#Setup_extra_disk
>
>
> At this point, the new slave is recognized by staging-master, and can be given
> jobs to process, but the slave immediately fails out the job with:
> exceptions.RuntimeError: Couldn't find executable for 'hg'
>
> Manually logging into the slave, I get:
> $ which hg
> which: hg: unknown command
>
> ...even though I can see /d/mercurial/hg.exe. By contrast when I login to one
> of the pre-existing slaves, I get:
>
> $ which hg
> /d/mercurial/hg.exe
>
>
> Still working on it.
Turns out to be problem with our refimage missing a recently added env.variable. I've updated https://wiki.mozilla.org/ReferencePlatforms/Win32.
moz2-win32-slave12 now works just fine.
Assignee | ||
Comment 11•16 years ago
|
||
moz2-win32-slave12.b.m.o now visible in production pool, and immediately started building.
Assignee | ||
Comment 12•16 years ago
|
||
moz2-win32-slave11.b.m.o
moz2-win32-slave13.b.m.o
...are both now running final tests in staging pool.
As soon as these test builds complete successfully, I'll move both of these to the production pool.
Assignee | ||
Comment 13•16 years ago
|
||
moz2-win32-slave11.b.m.o now enabled in production pool.
Assignee | ||
Comment 14•16 years ago
|
||
moz2-win32-slave13.b.m.o now enabled in production pool.
Comment 16•16 years ago
|
||
which of these is going into production, and which are staying in staging?
Assignee | ||
Updated•16 years ago
|
Priority: P1 → P2
Assignee | ||
Comment 17•16 years ago
|
||
Attachment #348784 -
Flags: review?(bhearsum)
Comment 18•16 years ago
|
||
Comment on attachment 348784 [details] [diff] [review]
add more win32 slaves to the pool
These need to be added to the mozilla-central win32-debug list and the tracemonkey list
Attachment #348784 -
Flags: review?(bhearsum) → review-
Assignee | ||
Comment 19•16 years ago
|
||
Good catch, thanks.
Attachment #348784 -
Attachment is obsolete: true
Attachment #348814 -
Flags: review?(bhearsum)
Updated•16 years ago
|
Attachment #348814 -
Flags: review?(bhearsum)
Attachment #348814 -
Flags: review+
Attachment #348814 -
Flags: checked‑in+
Assignee | ||
Comment 20•16 years ago
|
||
moz2-win32-slave16.b.m.o is now in production.
moz2-win32-slave15.b.m.o is now in production.
Assignee | ||
Comment 21•16 years ago
|
||
moz2-win32-slave17.b.m.o is now in production.
Assignee | ||
Comment 22•16 years ago
|
||
moz2-win32-slave18.b.m.o is now in production.
Thats all the slaves that *I* knew of. Is there anything left to do here, or can we now close this bug?
Assignee | ||
Comment 23•16 years ago
|
||
This bug, and all the dep.bugs are now done. Closing!
Status: NEW → RESOLVED
Closed: 16 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
•