This is the summary for test reports received on the
zope-tests list between 2014-12-27 00:00:00 UTC and 2014-12-28 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
[1] Still Failing - zopetoolkit_trunk - Build # 867
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
[2] winbot / ZODB_dev py_270_win32
[3] winbot / ZODB_dev py_270_win64
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 867
https://mail.zope.org/pipermail/zope-tests/2014-December/086279.html
[2] FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2014-December/086290.html
[3] FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2014-December/086291.html
I've worked through getting releases done for all the "stuck in alpha" ZTK
packages.
- All have their supported versions tested on Travis (I think), and
passing.
- I have pushed releases for all but one ('zope.ptresource', where I don't
have rights) to PyPI.
Something for your stocking. Enjoy the holidays, everyone!
Tres.
--
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com