http://blog.gmane.org/gmane.comp.web.zope.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.web.zope.devel/29536 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-11 00:00:00 UTC and 2013-06-12 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 # 294 [1] winbot / ZEO_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / ZODB_dev py_270_win64 [6] winbot / z3c.authenticator_py_265_32 [7] winbot / z3c.breadcrumb_py_265_32 [8] winbot / z3c.configurator_py_265_32 [9] winbot / z3c.contents_py_265_32 [10] winbot / z3c.coverage_py_265_32 [11] winbot / z3c.datagenerator_py_265_32 [12] winbot / z3c.form_py_265_32 [13] winbot / z3c.formui_py_265_32 [14] winbot / z3c.json_py_265_32 [15] winbot / z3c.jsontree_py_265_32 [16]</pre> Zope tests summarizer 2013-06-13T01:00:03 http://comments.gmane.org/gmane.comp.web.zope.devel/29535 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-10 00:00:00 UTC and 2013-06-11 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 # 293 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-12T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29533 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, download.zope.org seems to be. Bad because there is Plone hotfix release scheduled for toda 15h UTC... Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJRtwjYAAoJEADcfz7u4AZjoncLvRE3dS0RrWZmHmQvQ8WMAOxc 09JwPY9HkcD4ghblZv/jaLIHVpcSs3H6RU+bf+vGLiw6zEnYphKu7oZI9avjlY7Q NEfRiC1QLlyE8L/m45PL9nH8MzF+LhidOGRIxp989ME/ol8dOBmxoF4Fp7st5TZ5 nyidwjC+rKlywaoInvFVwgizezLxyt8ljBLHwOVS7T8Tr+xrYmMC9H4ifdWQvj/T +H/cF9byGWrne8tJIqCYzIvXC7vAMYk9qOfD38lCx4+F/v1xYG4EtYyGTHLSJXFV KS8j14PY248ZF0N/6OgNnw9EXz3WrNNehPz3h8iyzhnZgu/TvNXzSjqoKPAI+7z5 ZdcHkvM3HXdUZstMUy2qPa62J0T0MH7Sjo3N4Hn49+1ILo5r7fI1oZcg3/b9F8IT wFuWibMN3G7YUMgqFeDqkF1gb9+rWz5b17CzO9AgzMuvK/B3WZLJCGGB28Wsk74e /0dvKUjjb58LBooXNoDFIgVxrPEoQnI= =8HlV -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev&lt; at &gt;zope.org https://mail.zope.org/mailman/listinfo/zope-dev **</pre> Andreas Jung 2013-06-11T11:24:08 http://comments.gmane.org/gmane.comp.web.zope.devel/29532 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-09 00:00:00 UTC and 2013-06-10 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 # 292 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-11T01:00:03 http://comments.gmane.org/gmane.comp.web.zope.devel/29531 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-08 00:00:00 UTC and 2013-06-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 ---------------- Successful - zopetoolkit_trunk - Build # 291 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.datagenerator_py_265_32 [11] winbot / z3c.form_py_265_32 [12] winbot / z3c.formui_py_265_32 [13] winbot / z3c.json_py_265_32</pre> Zope tests summarizer 2013-06-10T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29530 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-07 00:00:00 UTC and 2013-06-08 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 # 290 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-09T01:00:03 http://comments.gmane.org/gmane.comp.web.zope.devel/29529 <pre>I have been trying to figure out which templating language to use with ZTFY. I really like mint. https://pypi.python.org/pypi/mint/0.5 It is simple, clean, small. It is like moinmoin, makes it very easy to create html. And you can create and inherit or override python functions that return a chunk of html. It also appears that it works as an html-free templating language for javascript or emails. PERFECT! I know one person who recommended it, he is using it with zope, although not with ZCA. He got rid of zope.publisher. Another person and I are thinking of using it. Has anyone tried it? Had a good or bad experience with it? Of course it would be great to find an egg that integrates mint into the ZCA. But perhaps it does not do multiple languages well. If you are curious here are my comments on the other templating languages. http://zopache.com/TemplatingLanguages Any comments on mint with zope would be most appreciated. Chris </pre> Christopher Lozinski 2013-06-08T03:32:23 http://comments.gmane.org/gmane.comp.web.zope.devel/29528 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-06 00:00:00 UTC and 2013-06-07 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 # 289 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-08T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29527 <pre>Hi all, does anyone can migrate z3c.recipe.i18n on Github? The last version doesn't work with Buildout 2.x and I want work on it. Thanks. -- Sebastien Douche &lt;sdouche&lt; at &gt;gmail.com&gt; Twitter: &lt; at &gt;sdouche / G+: +sdouche _______________________________________________ Zope-Dev maillist - Zope-Dev&lt; at &gt;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 ) </pre> Sebastien Douche 2013-06-07T15:45:44 http://comments.gmane.org/gmane.comp.web.zope.devel/29526 <pre>Hi A bit of context first: We have a zope application, using zope.schema to define our objects. The problem is, we have circular references, units contain references to persons and persons contain references to units. For schema validation, this is solved by subclassing zope.schema.Object and making it aware of reference objects and contained objects. So far so good. Now I'm working on z3c.schema2json (originally by Paul Wilson), allowing zope.schema defined objects to be converted to a dictionary structure. The problem I encounter here is that there is no awareness of reference or containment. This causes endless recursion going from person to unit back to person back to unit, . . A clean way to solve this, would be adding a marker interface IReference/ILazyLoad, . ., to the reference objects. If the serializer encounters the IReference interface, it can be skipped for serialization. The same concept could probably be used for the schema validation. To me the best place to add this marker </pre> Jan Van Hees 2013-06-07T06:45:23 http://comments.gmane.org/gmane.comp.web.zope.devel/29525 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-05 00:00:00 UTC and 2013-06-06 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 # 288 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-07T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29524 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-04 00:00:00 UTC and 2013-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 ---------------- Successful - zopetoolkit_trunk - Build # 287 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.datagenerator_py_265_32 [10] winbot / z3c.form_py_265_32 [11] winbot / z3c.formui_py_265_32 [12] winbot / z3c.json_py_265_32 [13] winbot / z3c.jsontree_py_265_32 [14]</pre> Zope tests summarizer 2013-06-06T01:00:03 http://comments.gmane.org/gmane.comp.web.zope.devel/29522 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-03 00:00:00 UTC and 2013-06-04 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 # 286 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [3] winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.breadcrumb_py_265_32 [6] winbot / z3c.configurator_py_265_32 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.coverage_py_265_32 [9] winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.json_py_265_32 [12] winbot / z3c.jsontree_py_265_32 [13] winbot / z3c.language.switch_py_265_32 [1</pre> Zope tests summarizer 2013-06-05T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29519 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The bloody state of the winbot at the moment seems tied to issues related to setuptools 0.6, distribute 0.5.4x, and zc.buildout. I put in some effort today on a branch to end-run the whole old-setuptools / distribute bit by updating buildout2 to use the newly-availabe (but not yet released to PyPI) setuptools 0.7. This version is the first release after the merge of old setuptools and distribute, and should be the preferred target for future work. My branch of buildout is here: https://github.com/tseaver/buildout/tree/use-setuptools-0.7 with a pull request to the main repo: https://github.com/buildout/buildout/pull/123 One issue that has to be worked around in the near term: the 0.7 release has been published via the bitbucket downloads page: but not pushed to the cheeseshop. I uploaded a hacked version of 'ez_setup.py' to deal with that interim problem here: http://dist.repoze.org/ez_setup-0.7.py and my buildout branch uses that version. I wo</pre> Tres Seaver 2013-06-04T01:25:25 http://comments.gmane.org/gmane.comp.web.zope.devel/29518 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-02 00:00:00 UTC and 2013-06-03 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 # 285 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.language.negotiator_py_265_32 [12] winbot / z3c.language.session_py_265_32 [13] winbot / z3c.pdftemplate_py_265_32 [14] winbot / z3c.</pre> Zope tests summarizer 2013-06-04T01:00:07 http://comments.gmane.org/gmane.comp.web.zope.devel/29513 <pre>This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-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 # 284 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.batching_py_265_32 [10] winbot / z3c.jsonrpc_py_265_32 [11] winbot / z3c.jsonrpcproxy_py_265_32 [12] winbot / z3c.language.negotiator_py_265_32 [13] winbot / z3c.language.session_py_265_32 [14] winbot / z3c.pdf</pre> Zope tests summarizer 2013-06-03T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29512 <pre>This is the summary for test reports received on the zope-tests list between 2013-05-31 00:00:00 UTC and 2013-06-01 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 # 283 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.language.negotiator_py_265_32 [12] winbot / z3c.language.session_py_265_32 [13] winbot / z3c.pdftemplate_py_265_32 [14] winbot / z3c.</pre> Zope tests summarizer 2013-06-02T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29511 <pre>This is the summary for test reports received on the zope-tests list between 2013-05-30 00:00:00 UTC and 2013-05-31 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 # 282 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.language.negotiator_py_265_32 [12] winbot / z3c.language.session_py_265_32 [13] winbot / z3c.pdftemplate_py_265_32 [14] winbot / z3c.</pre> Zope tests summarizer 2013-06-01T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29510 <pre>This is the summary for test reports received on the zope-tests list between 2013-05-29 00:00:00 UTC and 2013-05-30 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 # 281 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.batching_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.language.negotiator_py_265_32 [12] winbot / z3c.language.session_py_265_32 [13] winbot / z3c.pdftemplate_py_265_32 [14] winbot / z3c.</pre> Zope tests summarizer 2013-05-31T01:00:02 http://comments.gmane.org/gmane.comp.web.zope.devel/29506 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I have a buildout where I am using the 'pyamp' module. https://pypi.python.org/pypi/pyamp zc.buildout on my Raspberry PI tries to download and install the binary release package for Linux. Is there a way to force buildout to use source code distros only? Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJRpzd7AAoJEADcfz7u4AZj/0cLvR3tzsOJuYmeUxgCuVXCDoCb F0TPQyf9IapLtlqxiFjZ0KBQYu2BhgBag1yD7qAkvXlwd6I3d+hack0P8SxtkDvc RY0CxwDAe5I6W/T99VzeUm/2SiWKNAISDknyieOoyHHBaHqlwP3vgxZ0ZyWsxyxC dgUWuhJmmekTXdGC7n8vY1seuEuoKWhcpStkutuQojwyMYQctFMqiu7fXGDgqQdg VxuOfV5JqOH8Bt2PsoQEKniH6zM4uCOFwk6+ikCzMA24bBOiMjE6A1zhNCi0NmJh S/vNS60NZW5NZV8X7Y3yYkTxHG3wlUn6JSydOAfY9HdCW30TzUWupr70z2dSCxM5 iea071mvHCoKBX/aoO7lnKQc+tzChtW8iSzVuqNbXtdKzj0syy7emHglsxDx1wCY 7SEUq7Z08npI59RzgntEqE/aa4WpQ0AQJed8QKKL1KWSt/C2VWpoQ/N2l755dayS oudyN0YmycGrcQaXp8h3/SKLAKdi2Wg= =W2DV -----END PGP </pre> Andreas Jung 2013-05-30T11:26:51 http://comments.gmane.org/gmane.comp.web.zope.devel/29505 <pre>This is the summary for test reports received on the zope-tests list between 2013-05-28 00:00:00 UTC and 2013-05-29 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 ---------------- Fixed - zopetoolkit_trunk - Build # 280 [1] winbot / BTrees_py_265_32 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / persistent_py_265_32 [6] winbot / transaction_py_265_32 [7] winbot / z3c.baseregistry_py_265_32 [8] winbot / z3c.jsonrpc_py_265_32 [9] winbot / z3c.jsonrpcproxy_py_265_32 [10] winbot / z3c.language.negotiator_py_265_32 [11] winbot / z3c.language.session_py_265_32 [12] winbot / z3c.pdftemplate_py_265_32 [13] winbot / z3c.viewtemplate_py_265_32 [14] winbot / z3c.x</pre> Zope tests summarizer 2013-05-30T01:00:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.devel