On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <nore...@zope.org> wrote:

...

> [1]    FAILED  winbot / ZODB_dev py_265_win32
>        https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html
>
>
> [2]    FAILED  winbot / ZODB_dev py_265_win64
>        https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html
>
>
> [3]    FAILED  winbot / ZODB_dev py_270_win32
>        https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html
>
>
> [4]    FAILED  winbot / ZODB_dev py_270_win64
>        https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html

This is due to the release yesterday.

I can and will "fix" this, by providing a test extra, but this will only
cause no tests to run.  The fix may be needed for test of third-party
packages that depend on ZODB3 [test].

The winbot needs to be modified to run the tests for persistent,
BTrees, ZODB and ZEO separately.

>
> [5]    FAILED  winbot / zc.lockfile_py_265_32
>        https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html

I'll look at this today.

Jim

-- 
Jim Fulton
http://www.linkedin.com/in/jimfulton
Jerky is better than bacon! http://zo.pe/Kqm
_______________________________________________
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