Closed
Bug 658024
Opened 15 years ago
Closed 15 years ago
w32 builders spewing logs to stdout
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
(Whiteboard: [slavealloc])
Attachments
(1 file)
|
659 bytes,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
In staging, I'm seeing the w32 builders failing to log to twistd.log. The old buildbot.tac looks like
E:\builds\moz2_slave>type buildbot.tac
from twisted.application import service
from buildbot.slave.bot import BuildSlave
maxdelay = 300
buildmaster_host = 'production-master01.build.mozilla.org'
passwd = 'm0z1LLaTw0'
maxRotatedFiles = None
basedir = r'e:\builds\moz2_slave'
umask = 002
slavename = 'w32-ix-slave04'
usepty = 1
rotateLength = 1000000
port = 9010
keepalive = None
application = service.Application('buildslave')
try:
from twisted.python.logfile import LogFile
from twisted.python.log import ILogObserver, FileLogObserver
logfile = LogFile.fromFullPath("twistd.log", rotateLength=rotateLength,
maxRotatedFiles=maxRotatedFiles)
application.setComponent(ILogObserver, FileLogObserver(logfile).emit)
except ImportError:
# probably not yet twisted 8.2.0 and beyond, can't set log yet
pass
s = BuildSlave(buildmaster_host, port, slavename, passwd, basedir,
keepalive, usepty, umask=umask, maxdelay=maxdelay)
s.setServiceParent(application)
which is about the same as what slavealloc is handing out, so I'm not sure what the deal is.
| Assignee | ||
Comment 1•15 years ago
|
||
It's an ancient version of Twisted that doesn't log to a file by default on windows, apparently. 'buildbot start' adds teh --logfile parameter, and this seems to fix it ('course, you don't get log rotation..)
Assignee: nobody → dustin
Attachment #533399 -
Flags: review?(bhearsum)
Updated•15 years ago
|
Attachment #533399 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 2•15 years ago
|
||
checked in and deployed via puppet - I'll upgrade the w32 back in bug 616351.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•