The other day, Martin pointed out that my buildslave had gone off the reservation: on restarting it via the "buildbot start ~/buildarea" command - Martin noticed the slave had started throwing the DNS resolution error: closing stdin using PTY: True svn: PROPFIND request failed on '/projects/python/branches/py3k' svn: PROPFIND of '/projects/python/branches/py3k': Could not resolve hostname `svn.python.org': Temporary failure in name resolution (http://svn.python.org) program finished with exit code 1 Apparently, this has bothered a few buildbots. Some quick googling popped up the fix: http://buildbot.net/trac/wiki/UsingLaunchd After dropping the attached plist file in /Library/LaunchDaemons and setting the permissions right (and then chown -R'ing the existing buildarea for the buildbot user to buildbot:daemon) - running "sudo launchctl load org.python.buildbot.slave.plist" brought the buildbot back up in working order. Hopefully this helps out. -jesse -------------- next part -------------- A non-text attachment was scrubbed... Name: org.python.buildbot.slave.plist Type: application/octet-stream Size: 1146 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20090122/db48bcfa/attachment.obj>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4