On Thu, Jun 12, 2008 at 06:25:21PM +0200, ct@gocept.com wrote:
The Buildbot has detected a new failure of zc.lockfile on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/zc.lockfile/builds/100
Buildbot URL: http://zopebuildbot.whq.gocept.com/
Buildslave for this Build: local
Build Reason: The Nightly scheduler named 'zc.lockfile nightly' triggered this build Build Source Stamp: [branch zc.lockfile/trunk] HEAD Blamelist:
BUILD FAILED: failed test Logs are attached.
sincerely, -The Buildbot
A build/buildout.cfg A build/setup.py A build/src A build/src/zc A build/src/zc/__init__.py A build/src/zc/lockfile A build/src/zc/lockfile/__init__.py A build/src/zc/lockfile/tests.py A build/src/zc/lockfile/README.txt A build/README.txt U build Checked out revision 87335.
Creating directory '/home/ctheune/zope.org/slave/zc.lockfile/build/bin'. Creating directory '/home/ctheune/zope.org/slave/zc.lockfile/build/parts'. Creating directory '/home/ctheune/zope.org/slave/zc.lockfile/build/develop-eggs'. Generated script '/home/ctheune/zope.org/slave/zc.lockfile/build/bin/buildout'.
Upgraded: zc.buildout version 1.0.5, setuptools version 0.6c8; restarting. Generated script '/home/ctheune/zope.org/slave/zc.lockfile/build/bin/buildout'. Develop: '/home/ctheune/zope.org/slave/zc.lockfile/build/.' Installing test. Generated script '/home/ctheune/zope.org/slave/zc.lockfile/build/bin/test'.
Running tests at all levels Running unit tests: Running: ......
So, what happened there? Was the test runner process killed externally? Marius Gedminas -- Microsoft's entry in this cavalcade of horrors is Universal Plug and Play (UPnP). This is a protocol that allows [...] an end-user system to request a dynamic port-forwarding from the firewall to the box. Many network administrators will probably (rightly) recoil at letting applications on a Windows box dictate firewall policy. -- Anthony Baxter