-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/29/2013 08:00 PM, Zope tests summarizer wrote:
> [1]    FAILED  winbot / ZODB_dev py_270_win64 
> https://mail.zope.org/pipermail/zope-tests/2013-January/071764.html

I'm not terribly certain, but this looks like a timeout / race condition
on a test, perhaps due to load on the machine?


 Failure in test
c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt

 ----------------------------------------------------------------------
 File
"c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt",
line 220, in historical_connections.txt
 Failed example:
     [c in conns1 for c in conns2]
 Expected:
     [False, False, True, True]
 Got:
     [False, False, False, True]

The text above the failed example seems to expect that the first two
connections would have timed out / been garbage collected, but that the
second two would be fresh enough to be reused.


> [2]    FAILED  winbot / z3c.recipe.paster_py_265_32 
> https://mail.zope.org/pipermail/zope-tests/2013-January/071765.html

The same failure.  I reiterate that somebody who knows / cares about the
'zc.recipe.paster' project needs to step in an fix this failure, or else
we need to retire its nightly test run.



Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEIftQACgkQ+gerLs4ltQ5scgCdESe9ZLgWyKZwYPVxxKzvnPcN
diMAoKj/JEfukaFwUO9O9KzcsMo5go+T
=9qq4
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to