Stefan H. Holek wrote at 2006-9-10 17:14 +0200:
>So it looks like I have identified the bad test. It is
>ZODB.tests.testZODB.checkResetCachesAPI. When I suppress that test
>all goes well:
Maybe the failure of this test explains why "Refresh" no longer works?
--
Dieter
_
So it looks like I have identified the bad test. It is
ZODB.tests.testZODB.checkResetCachesAPI. When I suppress that test
all goes well:
$ python2.4 test.py -q -m '!^(ZEO|zope[.]app[.])' -t '!
checkResetCachesAPI' --all
Running unit tests:
The following test left new threads behind:
testABO
/me scratches head. I only see the error when I use the bot's command
line, a "normal" test run works fine.
$ python2.4 test.py -q --all
Running unit tests:
The following test left new threads behind:
testABOR (zope.server.ftp.tests.test_ftpserver.Tests)
New thread(s): [<_DummyThread(Dummy-36,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux
> zc-buildbot.
>
> Buildbot URL: http://buildbot.zope.org/
>
> Build Reason: changes
> Build Source Stamp: 7559
> Blamelist: flox,jinty,shh
>
> BUILD
