on Fri May 29 2009, "pycryptopp" <trac-yA4Be9i5DcKGglJvpFV4uA-AT-public.gmane.org> wrote:
> #22: pycryptocpp won't build on OpenSolaris 0906 > ------------------------+--------------------------------------------------- > Reporter: bewst | Owner: > Type: defect | Status: closed > Priority: major | Version: 0.5.1 > Resolution: fixed | Keywords: > Launchpad_bug: | > ------------------------+--------------------------------------------------- > > Comment(by zooko): > > Great! Thanks! Here's what you do: > > 1. Install buildbot -- http://buildbot.net > 2. Choose a name for your machine which will distinguish it from the > following set: ['slave-gutsy-tahoe', 'faust-osx', 'zandr-64', > 'buildbot.rubenkerkhof.com', 'tahoeslave-feisty', 'windows-cygwin-tahoe', > 'windows-native-tahoe', 'virtual1-edgy-tahoe', 'slave-etch-tahoe', > 'draco', 'gutsy', 'luther-dsl', 'windows-native', 'solaris-amd64-nexenta- > nooxie', 'linux-amd64-ubuntu-hardy-yukyuk', 'slave-osx-leopard', 'nooxie- > opensolaris', 'yukyuk', 'buildsl...@tahoecs2/slave-speed-colo', > 'mac-i386-osx-10.5-faust', 'slave1-testing-tahoe', 'mac- > amd64-osx-10.4.11-ootles', 'zandr-linkstation', 'mac- > amd64-osx-10.5-virtualzooko', 'slave3-dapper', 'windows-cygwin', 'slave3 > -dapper-tahoe'] > 3. Send your buildslave name and a secret password to > [email protected] . > 4. Run "buildbot create-slave $DIRECTORY dev.allmydata.com:10998 > $BUILDSLAVENAME $BUILDSLAVEPASSWORD > 5. Run "buildbot start $DIRECTORY" $ buildbot start /tank/testing/tahoe Following twistd.log until startup finished.. /usr/lib/python2.5/site-packages/buildbot-0.7.10p1-py2.5.egg/buildbot/scripts/logwatcher.py:48: PotentialZombieWarning: spawnProcess called, but the SIGCHLD handler is not installed. This probably means you have not yet called reactor.run, or called reactor.run(installSignalHandler=0). You will probably never see this process finish, and it may become a zombie process. env=os.environ, ERR: 'tail: cannot open input ' The buildmaster took more than 10 seconds to start, so we were unable to confirm that it started correctly. Please 'tail twistd.log' and look for a line that says 'configuration update complete' to verify correct startup. > Optionally then set up a buildslave to test Tahoe itself in addition to > the one that you just set up to test pycryptopp: make a different > directory and run the same steps as above but with master = > dev.allmydata.com:9987 instead of dev.allmydata.com:10998. You can use > the same buildslavename and password for both. Maybe after we get one working ;-) -- Dave Abrahams BoostPro Computing http://www.boostpro.com _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
