[Zope-dev] zope-tests - FAILED: 11, OK: 23
This is the summary for test reports received on the zope-tests list between 2012-07-03 00:00:00 UTC and 2012-07-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 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/065038.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065036.html [3]FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065030.html [4]FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065029.html [5]FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065033.html [6]FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065026.html [7]FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065034.html [8]FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065028.html [9]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065035.html [10] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065031.html [11] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/065032.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] zope-tests - FAILED: 11, OK: 23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/2012 05:33 AM, Patrick Gerken wrote: > zope.component 4.0.0 and zope.browserpage 3.12.2 are not compatible. > > Tres, I think you made browserpage compatible on trunk, can you > create a new release? Thanks for the diagnosis: I forgot that the winbot tests individual ZTK / zopeapp package trunks against released versions of all other packages. I have made forward-compatible 4.0.0 releases of zope.authentication, zope.browsermenu, and zope.browserpage, and bumped the ZTK trunk to include them. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/0N4UACgkQ+gerLs4ltQ4OggCgt9Vb6MIZ1Fe0Ys9yc+mp9jD4 qJEAn2SdbGUYQANjilcWGRxKqdZFHSDU =0tPH -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)
2012/7/4 Jan-Wijbrand Kolman > I guess Cykooz would know the revision of the common base? > > regards, jw > I do not remember the revision. But it certainly was from trunk branch. You can see the old revisions from SVN and my new here - https://bitbucket.org/cykooz/zope.intid/changesets ___ 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 7/3/12 15:06 , Hanno Schlichting wrote: > On Tue, Jul 3, 2012 at 1:56 PM, Jan-Wijbrand Kolman > 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. Ow, well, yes you are right. I didn't investigate too deeply either and I do not know the revision the fork was based on. Maybe I just didn't look hard enough. I just wanted to see if we could get a little feedback by posting the diff over here, instead for others to have to go through this just see what the proposed changes are. Being the messenger so to say. Did you stop looking at the diff once you noticed it was created suboptimally? Would it help to find out the base revision and post a diff again? I guess Cykooz would know the revision of the common base? 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-tests - FAILED: 11, OK: 23
zope.component 4.0.0 and zope.browserpage 3.12.2 are not compatible. Tres, I think you made browserpage compatible on trunk, can you create a new release? Or anybody can add me as a package maintainer on pypi, I am do3cc. On Wed, Jul 4, 2012 at 11:05 AM, Patrick Gerken wrote: > On Wed, Jul 4, 2012 at 3:00 AM, Zope tests summarizer > wrote: >> 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 > > I didn't check ALL of the failures but the ones I checked all > complayed that the layer attribute of browser:page is unknown. > Apparently I still don't understand zcml enough, because I didn't find > out, which package really provides this. > There were some changes in zope.browserpage related to layers, but > they aren't released as eggs yet and the test uses the eggified > version of browser.page zope.publisher got a new release before the > first failure, But I don't understand how this could affect the > failure. > Maybe somebody else here has an idea? >> >> >> ___ >> 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.
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 23
On Wed, Jul 4, 2012 at 3:00 AM, Zope tests summarizer wrote: > 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 I didn't check ALL of the failures but the ones I checked all complayed that the layer attribute of browser:page is unknown. Apparently I still don't understand zcml enough, because I didn't find out, which package really provides this. There were some changes in zope.browserpage related to layers, but they aren't released as eggs yet and the test uses the eggified version of browser.page zope.publisher got a new release before the first failure, But I don't understand how this could affect the failure. Maybe somebody else here has an idea? > > > ___ > 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 )
