zope-tests - FAILED: 1, OK: 13
This is the summary for test reports received on the zope-tests list between 2014-05-15 00:00:00 UTC and 2014-05-16 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 # 640 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 / 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 / zope.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-May/082193.html
On Sat, May 17, 2014 at 01:00:01AM +0200, Zope tests summarizer wrote:
This is the summary for test reports received on the zope-tests list between 2014-05-15 00:00:00 UTC and 2014-05-16 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 # 640 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 / zope.i18n_py_265_32
Something is seriously weird with timezones on winbot and/or pytz: AssertionError: u'2. Januar 2003 21:48:01 +053' != '2. Januar 2003 21:48:01 +100' Failure in test testFormatRealDateTime (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 385, in testFormatRealDateTime '2. Januar 2003 21:48:01 +100') File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: u'2. Januar 2003 21:48:01 +053' != '2. Januar 2003 21:48:01 +100' Failure in test testFormatTimeZone (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 422, in testFormatTimeZone '-500') File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: u'-504' != '-500' Failure in test testParseRealDateTime (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 278, in testParseRealDateTime tzinfo=pytz.timezone('Europe/Berlin'))) File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: datetime.datetime(2003, 1, 2, 21, 48, 1, tzinfo=pytz.FixedOffset(60)) != datetime.datetime(2003, 1, 2, 21, 48, 1, tzinfo=<DstTzInfo 'Europe/Berlin' LMT+0:53:00 STD>) I can reproduce locally. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Sun, May 18, 2014 at 09:34:49PM +0300, Marius Gedminas wrote:
On Sat, May 17, 2014 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1] winbot / zope.i18n_py_265_32
Something is seriously weird with timezones on winbot and/or pytz:
AssertionError: u'2. Januar 2003 21:48:01 +053' != '2. Januar 2003 21:48:01 +100' Failure in test testFormatRealDateTime (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 385, in testFormatRealDateTime '2. Januar 2003 21:48:01 +100') File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: u'2. Januar 2003 21:48:01 +053' != '2. Januar 2003 21:48:01 +100'
Looks like the Olsen database picked up a few historical German timezones, exposing a long-standing bug in zope.i18n's test suite. Should be fixed with https://github.com/zopefoundation/zope.i18n/commit/58051dcb365502a40f5a691af... Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer