On Mon, Dec 3, 2012 at 3:15 AM, Adam GROSZER <agroszer.ll@gmail.com> wrote:
Hello,
On 12/02/2012 02:55 PM, Jim Fulton wrote:
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <noreply@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.
I think the winbot does the right job. Those tests are running against
svn://svn.zope.org/repos/main/ZODB/trunk
Now the tests pass as you added [test] back:
Ah, there was a bug in the buildout config, which I just fixed. There's no way that ZODB should be depending on ZODB3, even in the buildout. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm