Re: zope-tests - FAILED: 5, OK: 42

Gediminas Paulauskas <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <CAH+bPgh2BiNO3qtHsNT-hJzC4PSWiHmLXAcQqOoRSX-vf-nE-g@mail.gmail.com>
2011/11/30 Tres Seaver <[email protected]>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> [1]    FAILED  winbot / zope.keyreference_py_265_32
>> https://mail.zope.org/pipermail/zope-tests/2011-November/053374.html
>>
>>
>> [2]    FAILED  winbot / ztk_dev py_265_win32
>> https://mail.zope.org/pipermail/zope-tests/2011-November/053375.html
>>
>>
>> [3]    FAILED  winbot / ztk_dev py_265_win64
>> https://mail.zope.org/pipermail/zope-tests/2011-November/053376.html
>>
>>
>> [4]    FAILED  winbot / ztk_dev py_270_win32
>> https://mail.zope.org/pipermail/zope-tests/2011-November/053377.html
>>
>>
>> [5]    FAILED  winbot / ztk_dev py_270_win64
>> https://mail.zope.org/pipermail/zope-tests/2011-November/053378.html
>
>
> All five failures are due to the removal of 'zope.testing' from the
> 'tests_require' of zope.keyreference, and look like::

Oops. I broke a module not touched for years the last minute before release.

I fixed this failure by avoiding zope.testing, not re-adding it.
Released as zope.keyreference 3.6.4

Strangely, tests passed for me in zope.keyreference/bin/test, that's
why I was not aware of the problem.

But now I tested as buildbot does from
zopetoolkit/bin/test-ztk-zope.keyreference could reproduce and fix it.

-- 
Gediminas
_______________________________________________
Zope-Dev maillist  -  [email protected]
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 )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.