-----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 +0000, 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 tseaver@palladion.com Palladion Software "Excellence by Design" http://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-----