Am 02.05.2012 um 03:00 schrieb Zope tests summarizer:
Non-OK results
--
[1]UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2012-May/061274.html
[2]UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64
On Wed, May 02, 2012 at 08:24:02AM +0200, Michael Howitz wrote:
Am 02.05.2012 um 03:00 schrieb Zope tests summarizer:
Non-OK results
--
[1]UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2012-May/061274.html
[2]
On Wed, May 2, 2012 at 3:40 PM, Adam GROSZER agroszer...@gmail.com wrote:
or why that package gets included
Adding zc.sourcefactory to the ZTK was a conscious choice. It was
popular and often used in Zope 3-style projects, maybe even part of
core Grok and BlueBream.
We could remove it from ZTK
This is the summary for test reports received on the
zope-tests list between 2012-05-01 00:00:00 UTC and 2012-05-02 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation: