zope-tests - FAILED: 2, OK: 13
This is the summary for test reports received on the zope-tests list between 2014-09-01 00:00:00 UTC and 2014-09-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: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 750 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.pdftemplate_py_265_32 [2] winbot / zope.i18n_py_265_32 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 winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-September/083685.html [2] FAILED winbot / zope.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-September/083684.html
On Wed, Sep 03, 2014 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-September/083685.html
ReportLab 3.1.8 doesn't support Python 2.6, it says so right in the PyPI classifiers. In fact ReportLab 3.0 doesn't support Python 2.6 either. And z3c.pdftemplate requires ReportLab >= 3.0 since https://github.com/zopefoundation/z3c.pdftemplate/commit/16c16f0d5929fd7ce41... Suggestion: turn off the Python 2.6 builder for z3c.pdftemplate, replace it with a Python 2.7 builder.
[2] FAILED winbot / zope.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-September/083684.html
Something interesting: Failure in test testParseTimeZoneNames (zope.i18n.tests.test_formats.TestDateTimeFormat) Traceback (most recent call last): File "c:\Python26_32\lib\unittest.py", line 279, in run testMethod() File "c:\buildslave\zope.i18n\build\src\zope\i18n\tests\test_formats.py", line 327, in testParseTimeZoneNames self.assertEqual(dt.tzinfo.tzname(dt), 'EST') File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: 'AEDT' != 'EST' I can reproduce locally with 'tox', but only on Python 3.4 -- all other Python versions pass the tests! No codebase changes since July 23, so it must be today's date (or perhaps a new version of pytz?) that causes this test to fail. Hey, a new version of pytz would explain things -- all my tox environments have the old one, but the .tox/py34 virtualenv is brand new. And pytz 2014.7 was released on September 1st. Should be fixed in https://github.com/zopefoundation/zope.i18n/commit/04af83794742b1a9ca7cd787a... Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer