Closed
Bug 656441
Opened 13 years ago
Closed 13 years ago
redeploy runslave.py on winxp
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
(Whiteboard: [slavealloc])
Maybe I should build an OPSI package for it this time!
The version of runslave.py deployed did not have the nagios reporting code in it.
Assignee | ||
Updated•13 years ago
|
Whiteboard: [slavealloc]
Assignee | ||
Comment 1•13 years ago
|
||
Need to fix bug 656450 first - name resolution is broken on windows.
Depends on: 656450
Assignee | ||
Comment 2•13 years ago
|
||
Deployed via SSH and http://people.mozilla.org/~dmitchell/xp.bat to all of the XP talos slaves, including talos-r3-xp-ref.
wget -O c:\runslave.py http://hg.mozilla.org/build/puppet-manifests/raw-file/tip/modules/buildslave/files/runslave.py
wget -O "c:\Documents and Settings\cltbld\Start Menu\Programs\Startup\startTalos.bat" http://hg.mozilla.org/build/puppet-manifests/raw-file/tip/modules/buildslave/files/startTalos-xp.bat
Nagios has noticed:
17:37 < nagios> talos-r3-xp-030.build.scl1:buildbot-start is OK: runslave.py executed
17:38 < nagios> talos-r3-xp-035.build.scl1:buildbot-start is OK: runslave.py executed
17:38 < nagios> talos-r3-xp-019.build.scl1:buildbot-start is OK: runslave.py executed
17:39 < nagios> talos-r3-xp-014.build.scl1:buildbot-start is OK: runslave.py executed
17:40 < nagios> talos-r3-xp-023.build.scl1:buildbot-start is OK: runslave.py executed
...
I confirmed that Buildbot is running on -030.
So I think this is fixed.
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
•