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
org.python.buildbot.slave.plist
Description: Binary data
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com