Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html These two are both the segfault-at-exit issue. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3rr3oACgkQ+gerLs4ltQ7S5wCeOlLJiSalEwFi78KxTwdWYhBW jHMAoIVtBwTjbGgVpAsA/oltZkYoOqDG =qHVi -END PGP SIGNATURE- ___ 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: 9, OK: 72
On Sun, Jun 5, 2011 at 6:31 PM, Tres Seaver tsea...@palladion.com wrote: [1] FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html [2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html These two are both the segfault-at-exit issue. I finally took the time to install me a virtual machine with Ubuntu 64bit on it. And I was able to reproduce the issue! It's not a segfault at exit, but actually happens inside a test: test_interfaces (Acquisition.tests) (0.001 s) test_mixed_explicit_and_explicit (Acquisition.tests)Segmentation fault Or to get the issue quicker: $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault I haven't yet tried to debug the problem itself. Hanno ___ 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: 9, OK: 72
On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting ha...@hannosch.eu wrote: Or to get the issue quicker: $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault I haven't yet tried to debug the problem itself. Here's some more info: The last successful build was #256 on Wed Apr 27 02:06:59 2011 which build revision 121465 The first failing build was #257 on Wed Apr 27 15:19:46 2011 which build revision 121473 Looking at the SVN changelog of Zope trunk, there were changes in r121460 and r121502. So the two builds used the exact same code, but still produced a different result. So it must be a change in the config of the buildslave that triggered this. There's no Python 2.7 release anywhere close to April this year, so I'm pretty sure both builds used the same Python 2.7.1. What caused the failure is a mystery to me. Hanno ___ 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: 9, OK: 72
On Sun, Jun 5, 2011 at 8:57 PM, Hanno Schlichting ha...@hannosch.eu wrote: On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting ha...@hannosch.eu wrote: $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault Here's some more info: The last successful build was #256 on Wed Apr 27 02:06:59 2011 which build revision 121465 The first failing build was #257 on Wed Apr 27 15:19:46 2011 which build revision 121473 Looking at the SVN changelog of Zope trunk, there were changes in r121460 and r121502. So the two builds used the exact same code, but still produced a different result. So it must be a change in the config of the buildslave that triggered this. There's no Python 2.7 release anywhere close to April this year, so I'm pretty sure both builds used the same Python 2.7.1. What caused the failure is a mystery to me. I see that Jan-Jaap did some unrelated changes to the buildslave config on that day (http://zope3.pov.lt/trac/changeset/121467/Sandbox/janjaapdriessen/buildbot). Jan-Jaap: Do you remember doing anything else on that day? Like upgrading the operating system, installing new OS packages or anything that could cause the sudden failure? Hanno ___ 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] Getting translation of python code string to work
Hi Morten, OK. Well I have this function now: def _(msgid, request): language = request['LANGUAGE'] return translate(msgid, domain='SimpleChat', target_language=language) Which sends all the relevant bits to the translate function. But, this doesn't work either, and I can see it is because the interpolate function call is used in translate. It seems you misunderstood my explanation (or I misunderstood yours), but are you trying to use your custom _() function instead of using a MessageFactory? the translation() function should be used WITH the results of calling MessageFactory() objects, not INSTEAD of them. First you create MessageFactory() objects in your code when creating messages, preferably as early and as little as possible. THEN, you call translate() on them, as late as possible, and as close as possible to the time where the translation is to be transmitted to the user. So do I need to setup some utility? In theory, IMessageDomain utilities need to be registered, but if translations are working inside Page Templates, then this is already the case. These utilities need to be configured before the translate() call happens (for example, when it is called implicitly during ZPT rendering), but don't need to be configured yet when calling _(some message) (assuming the _ object is a MessageFactory instance). I hope I'm not making this even more of a mess for you to understand... Cheers, Leo On Wed, Jun 1, 2011 at 09:02, li...@nidelven-it.no wrote: [...] On Tue, May 31, 2011 at 13:19, li...@nidelven-it.no wrote: Hi, I have a oldschool style Zope 2 product, which has an i18n directory containing translations. Using i18n:domain=SimpleChat in this product works fine in the page templates, Well, ZPTs generate message objects automatically from translated content, but they also explicitly translate all the message objects they get during interpolation between the literal parts of the template and the dynamically generated ones. but when I start translating text in a Python module using _(Translate me) I just get English text (instead of Norwegian, which is what I want). When you say I just get English text, what does exactly get mean in terms of code? Mind you, if you simple call unicode(message) you'll most likely only get the English version back. Same thing if you do: usome other string: %s % message To get an actual translation, you need to call zope.i18n.translate(message), eventually passing the target_languate=... parameter. Take a look at the zope.i18n module for details, specifically the translate() and negotiate() functions. OK. Well I have this function now: def _(msgid, request): language = request['LANGUAGE'] return translate(msgid, domain='SimpleChat', target_language=language) Which sends all the relevant bits to the translate function. But, this doesn't work either, and I can see it is because the interpolate function call is used in translate. So do I need to setup some utility? -Morten ___ 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 )
[Zope-dev] zope-tests - FAILED: 14, OK: 72
This is the summary for test reports received on the zope-tests list between 2011-06-04 00:00:00 UTC and 2011-06-05 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 Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux [1]Repository policy check found errors in 305 projects Total languishing bugs for zope2: 0 [2]Total languishing bugs for zope: 58 [3]Total languishing bugs for zopeapp: 2 [4]Total languishing bugs for zopetoolkit: 199 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 [5]Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.13_win-py2.6 slave-win Zope Buildbot / zope2.13_win-py2.7 slave-win Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 [6]Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit_win-py2.5 slave-win Zope Buildbot / zopetoolkit_win-py2.6 slave-win Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [7]winbot / z3c.coverage_py_265_32 [8]winbot / z3c.rml_py_265_32 [9]winbot / zc_buildout_dev py_254_win32 [10] winbot / zc_buildout_dev py_265_win32 [11] winbot / zc_buildout_dev py_265_win64 [12] winbot / zc_buildout_dev py_270_win32 [13] winbot / zc_buildout_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 [14] winbot / ztk_11 py_270_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]FAILED Repository policy check found errors in 305 projects https://mail.zope.org/pipermail/zope-tests/2011-June/042595.html [2]FAILED Total languishing bugs for zope: 58 https://mail.zope.org/pipermail/zope-tests/2011-June/042592.html [3]FAILED Total languishing bugs for zopeapp: 2 https://mail.zope.org/pipermail/zope-tests/2011-June/042590.html [4]FAILED Total languishing bugs for zopetoolkit: 199
