[Zope-dev] zope-tests - FAILED: 7, OK: 17
This is the summary for test reports received on the zope-tests list between 2012-12-08 00:00:00 UTC and 2012-12-09 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]Repository policy check found errors in 277 projects Successful - zopetoolkit_trunk - Build # 101 Successful - zopetoolkit_trunk_app - Build # 85 [2]Total languishing bugs for zope2: 4 [3]Total languishing bugs for zope: 72 [4]Total languishing bugs for zopeapp: 1 [5]Total languishing bugs for zopetoolkit: 205 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [6]winbot / z3c.recipe.paster_py_265_32 [7]winbot / zope.app.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 Repository policy check found errors in 277 projects https://mail.zope.org/pipermail/zope-tests/2012-December/069871.html [2]FAILED Total languishing bugs for zope2: 4 https://mail.zope.org/pipermail/zope-tests/2012-December/069870.html [3]FAILED Total languishing bugs for zope: 72 https://mail.zope.org/pipermail/zope-tests/2012-December/069869.html [4]FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2012-December/069867.html [5]FAILED Total languishing bugs for zopetoolkit: 205 https://mail.zope.org/pipermail/zope-tests/2012-December/069868.html [6]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069866.html [7]FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069865.html ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] DateTime issues with negative offsets
Here's Guido's official explanation for the divmod behaviour: http://python-history.blogspot.com.br/2010/08/why-pythons-integer-division-floors.html IMHO we should treat negative offsets specially, doing the divmod() with -60 in that case. Regards, Leo On Fri, Dec 7, 2012 at 5:22 PM, Juan A. Diaz wrote: > secconds / 60 ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope-tests - FAILED: 2, OK: 20, UNKNOWN: 1
2012/12/7 Tres Seaver : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12/07/2012 01:11 PM, Gediminas Paulauskas wrote: >> 2012/12/7 Tres Seaver : >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >>> On 12/07/2012 01:52 AM, Marius Gedminas wrote: >> [3]FAILED winbot / zope.app.i18n_py_265_32 >> https://mail.zope.org/pipermail/zope-tests/2012-December/069796.html >> >>> >> > Error in test testNoTargetLanguage >>> (zope.app.i18n.tests.test_translationdomain.TestTranslationDomain) Traceback (most recent call last): File "c:\Python26_32\lib\unittest.py", line 279, in run testMethod() File "c:\eggs\zope.i18n-3.8.0-py2.6.egg\zope\i18n\tests\test_itranslationdomain.py", > line 99, in testNoTargetLanguage eq(translate('short_greeting', context=context, default=42), 42) File "c:\buildslave\zope.app.i18n\build\src\zope\app\i18n\translationdomain.py", > line 74, in translate catalog_names = self._catalogs.get(target_language, []) TypeError: Object has default comparison >>> >>> Here, the 'target_langeage' returned by the negotiator is None, >>> which the OOBTree is refusing to treat as a key (because its >>> comparison semantics are undefined across process boundaries / >>> Python versions):: >>> >> from BTrees.OOBTree import OOBTree x = OOBTree() x[None] = 1 >>> Traceback (most recent call last): File "", line 1, in >>> TypeError: Object has default comparison >>> >>> Such keys haven't been allowed since:: >>> >>> r117933 | jim | 2010-10-26 17:14:00 -0400 (Tue, 26 Oct 2010) | 7 >>> lines >>> >>> Bug Fixed - BTrees allowed object keys with insane comparison. >>> (Comparison inherited from object, which compares based on >>> in-process address.) Now BTrees raise TypeError is an attempt is >>> made to save a key with comparison inherited from object. (This >>> doesn't apply to old-style class instances.) >> >> The error happens in get, not set, should it? > > The C code throws the error whenever dealing with a user-supplied key > which cannot be safely compared to existing keys. > >> Otherwise, a patch for zope.app.i18n to fix this case is attached >> (not committed). > > +1 for your patch. ok, committed. -- Gediminas ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )