Re: [Zope-dev] zope-tests - FAILED: 2, OK: 22
On Tue, Jul 03, 2012 at 01:00:04AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2012-07-01 00:00:00 UTC and 2012-07-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
Zope 3.4 Known Good Set / py2.4-32bit-linux
[1]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-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
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
[2]winbot / zope.app.container_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 Zope 3.4 Known Good Set / py2.4-64bit-linux
https://mail.zope.org/pipermail/zope-tests/2012-July/064968.html
Temporary Internet resolution trouble in the 'svn up' step.
[2]FAILED winbot / zope.app.container_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-July/064969.html
Failures in
zope.app.container.browser.tests.test_directive.test_containerViews
zope.app.container.browser.tests.test_directive.test_containerViews_layer
The tests are hard to read. Here's the diff for the first failure:
--- expected
+++ actual
@@ -12,17 +12,17 @@
(function provideInterface,
InterfaceClass zope.app.container.browser.tests.test_directive.I),
('view',
- (InterfaceClass zope.app.container.browser.tests.test_directive.I,
- InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
+ InterfaceClass zope.app.container.browser.tests.test_directive.I,
'contents.html',
- InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest),
+ InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest,
+ InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
(function provideInterface,
InterfaceClass zope.app.container.browser.tests.test_directive.I),
('view',
- (InterfaceClass zope.app.container.browser.tests.test_directive.I,
- InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
+ InterfaceClass zope.app.container.browser.tests.test_directive.I,
'index.html',
- InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest),
+ InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest,
+ InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
('adapter',
(InterfaceClass zope.app.container.browser.tests.test_directive.I,
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital 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: 2, OK: 22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/03/2012 03:06 AM, Marius Gedminas wrote:
On Tue, Jul 03, 2012 at 01:00:04AM +, Zope tests summarizer
wrote:
This is the summary for test reports received on the zope-tests list
between 2012-07-01 00:00:00 UTC and 2012-07-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
Zope 3.4 Known Good Set / py2.4-32bit-linux [1]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-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 winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot
/ ZODB_dev py_270_win64 [2]winbot /
zope.app.container_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 Zope 3.4 Known Good Set / py2.4-64bit-linux
https://mail.zope.org/pipermail/zope-tests/2012-July/064968.html
Temporary Internet resolution trouble in the 'svn up' step.
[2]FAILED winbot / zope.app.container_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-July/064969.html
Failures in
zope.app.container.browser.tests.test_directive.test_containerViews
zope.app.container.browser.tests.test_directive.test_containerViews_layer
The tests are hard to read. Here's the diff for the first failure:
--- expected +++ actual @@ -12,17 +12,17 @@ (function
provideInterface, InterfaceClass
zope.app.container.browser.tests.test_directive.I), ('view', -
(InterfaceClass zope.app.container.browser.tests.test_directive.I, -
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer), +
InterfaceClass zope.app.container.browser.tests.test_directive.I,
'contents.html', - InterfaceClass
zope.publisher.interfaces.browser.IBrowserRequest), +
InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest, +
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer), (function
provideInterface, InterfaceClass
zope.app.container.browser.tests.test_directive.I), ('view', -
(InterfaceClass zope.app.container.browser.tests.test_directive.I, -
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer), +
InterfaceClass zope.app.container.browser.tests.test_directive.I,
'index.html', - InterfaceClass
zope.publisher.interfaces.browser.IBrowserRequest), +
InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest, +
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer), ('adapter',
(InterfaceClass zope.app.container.browser.tests.test_directive.I,
InterfaceClass
zope.publisher.interfaces.browser.IDefaultBrowserLayer),
I expect that yesterday's release of zope.component 4.0.0 will fix this
failure: that release changes the discriminator for the 'view'
directive, making it structurally similar to the corresopnding double
adapter. In particular, the request type (layer') used to be tacked on
to the end of the discriminator; it now gets passed as part of the
requires tuble (which is where it will actually be looked up).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/yqqkACgkQ+gerLs4ltQ5OSACfUGO1PMaztDVL1MxxgWa0NCH3
ZJsAoI3uJXBv4aJe3S3CNbPHtycJOShZ
=94lS
-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] SVN: zope.app.locales/trunk/ In version 3.7.2 msgids and default values where forced to be unicodes. This
Am 29.06.2012 um 19:45 schrieb Tres Seaver: […] Hmm, I'm running into a test failure where the Message constructor blows up with a decode error for the 'default' value here. Does that ring any bells for anyone? I know we can't be depending on a sys.setdefaultencoding hack. Sorry for the delayed response. I ran the tests of zope.app.locales with Python 2.5, 2.6 and 2.7. I did not get any errors. Which Pyhton version did you use? What does the traceback look like? Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com · Tel +49 345 1229889-8 Python, Pyramid, Plone, Zope · consulting, development, hosting, operations ___ 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] SVN: zope.app.locales/trunk/ In version 3.7.2 msgids and default values where forced to be unicodes. This
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/2012 05:07 AM, Michael Howitz wrote: Am 29.06.2012 um 19:45 schrieb Tres Seaver: […] Hmm, I'm running into a test failure where the Message constructor blows up with a decode error for the 'default' value here. Does that ring any bells for anyone? I know we can't be depending on a sys.setdefaultencoding hack. Sorry for the delayed response. I ran the tests of zope.app.locales with Python 2.5, 2.6 and 2.7. I did not get any errors. Which Pyhton version did you use? What does the traceback look like? Thanks for checking back. I cleared away the environment and rebuilt, and the issue went away. I'm planning to pretend it never happened. :) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/yua8ACgkQ+gerLs4ltQ5FpgCg3MOTIimTGPCbluE52NQBRs2W yCcAn0QIFCy3gFbZq8yZdu+6ZFAICLSI =RgN1 -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.intid and zope.keyreference.interfaces.NotYet exception (patch)
On 1/24/12 23:49 , Cykooz wrote: 2012/1/25 Marius Gedminas mar...@gedmin.as: http://foundation.zope.org/agreements is where you can find the committer agreement form. Thanks. But I have one problem. I do not know any of the existing Committer who can vouch for me. Bringing up a rather old thread: Cykooz, was there any kind of follow up on this discussion? Are you basically using a forked zope.keyreference for the time being? Kind regards, jw ___ 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.intid and zope.keyreference.interfaces.NotYet exception (patch)
2012/7/3 Jan-Wijbrand Kolman janwijbr...@gmail.com Are you basically using a forked zope.keyreference for the time being? No, I do not use a forked zope.keyreference. I used my fork of the zope.intid. ___ 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] [ZODB-Dev] RFC: release persistent as a standalone package
On Mon, Jul 2, 2012 at 7:35 PM, Alan Runyan runy...@gmail.com wrote: I would like to release a '4.0.0' version of the package, and switch the ZODB trunk to pull it in as a dependency (deleting the currently included (older) copy of persistent). One possible issue is that I have not (yet) made the C extensions work under Python 3.2: I don't know whether that should be a blocker for a release. I do not believe its a blocker. That is a feature that could be added. Comments? You rock. +1 ___ 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.intid and zope.keyreference.interfaces.NotYet exception (patch)
On Tue, Jul 3, 2012 at 1:56 PM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: At the end of this post, I pasted the diff from the current zope.intid trunk against your fork on bitbucket. Maybe this would make it easier for others to comment on it? It would be easier to read if you did the diff against the base version the fork was started from. Or otherwise update the fork with the changes done in the meantime. I see a bunch of unrelated changes in there, like the implements/implementer changes. I'm not sure what else is unrelated to the proposed change. 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.intid and zope.keyreference.interfaces.NotYet exception (patch)
Hi Kirill Why not just implement your own package and use this enhanced IntIds utility from there in your project? Regards Roger Ineichen _ END OF MESSAGE -Ursprüngliche Nachricht- Von: zope-dev-boun...@zope.org [mailto:zope-dev-boun...@zope.org] Im Auftrag von Cykooz Gesendet: Dienstag, 10. Januar 2012 23:28 An: zope-dev Betreff: [Zope-dev] zope.intid and zope.keyreference.interfaces.NotYet exception (patch) Hi, I created a patch for a package zope.intid that almost completely solves the problem with the zope.keyreference.interfaces.NotYet exception. I implemented a deferred indexing of objects added to the container which is not connected to the ZODB. As soon as the container is added to the ZODB - all deferred objects will be indexed. I also added a marker IIntIdsDisabled for marking objects that must not be indexed. I would be grateful if someone could look at my changes and merge them into the main branch. My fork of zope.intid - https://bitbucket.org/cykooz/zope.intid/src PS: Sorry for my English. --- Cykooz (Kirill Kuzminykh) ___ 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 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.intid and zope.keyreference.interfaces.NotYet exception (patch)
2012/7/3 Roger d...@projekt01.ch Hi Kirill Why not just implement your own package and use this enhanced IntIds utility from there in your project? Do you think that anyone else does not need the fix that I did? This error in the zope.intid completely negates the whole transparency in working with persistent objects. Due it is necessary to use various tricks, which impairs the understanding of how the program works. My patch does not break backwards compatibility and do not require additional changes to the code of existing components. So why not merge it into the zope.intid, instead of create a cykooz.intid? ___ 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: 11, OK: 23
This is the summary for test reports received on the zope-tests list between 2012-07-02 00:00:00 UTC and 2012-07-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 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-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 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.app.applicationcontrol_py_265_32 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.component_py_265_32 [4]winbot / zope.app.container_py_265_32 [5]winbot / zope.app.exception_py_265_32 [6]winbot / zope.app.generations_py_265_32 [7]winbot / zope.app.publisher_py_265_32 [8]winbot / zope.app.rotterdam_py_265_32 [9]winbot / zope.app.session_py_265_32 [10] winbot / zope.app.testing_py_265_32 [11] winbot / zope.app.zcmlfiles_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.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064994.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065004.html [3]FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064997.html [4]FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064996.html [5]FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065000.html [6]FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064992.html [7]FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065002.html [8]FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064995.html [9]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065003.html [10] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064998.html [11] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064999.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 )
