Re: [Zope-dev] zope-tests - FAILED: 29, OK: 15
On 08/27/2012 08:02 PM, Marius Gedminas wrote: On Mon, Aug 27, 2012 at 03:26:28PM +0200, Adam GROSZER wrote: Well, 3.4 KGS is not really interesting anymore, but it would be pretty helpful to have the same individual packages tested somewhere on linux as winbot does. Anyone? Ideas? Time? http://travis-ci.org/ ? That seems to be closely tied with github. Or do I miss there something? -- Best regards, Adam GROSZER -- Quote of the day: If there is anything we wish to change in the child, we should first examine it and see whether it is something that could better be changed in ourselves. - C.G. Jung ___ 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: 13, OK: 14, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2012-08-26 00:00:00 UTC and 2012-08-27 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 [1]UNKNOWN : Zope-trunk Python-2.6.8 : Linux [2]UNKNOWN : Zope-trunk Python-2.7.3 : 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 winbot / ZODB_dev py_265_win32 [3]winbot / z3c.datagenerator_py_265_32 [4]winbot / z3c.formui_py_265_32 [5]winbot / z3c.layer.pagelet_py_265_32 [6]winbot / z3c.menu.ready2go_py_265_32 [7]winbot / zc_buildout_dev py_254_win32 1.6.x [8]winbot / zc_buildout_dev py_265_win32 1.6.x [9]winbot / zc_buildout_dev py_265_win32 master [10] winbot / zc_buildout_dev py_265_win64 1.6.x [11] winbot / zc_buildout_dev py_265_win64 master [12] winbot / zc_buildout_dev py_270_win32 1.6.x [13] winbot / zc_buildout_dev py_270_win32 master [14] winbot / zc_buildout_dev py_270_win64 1.6.x [15] winbot / zc_buildout_dev py_270_win64 master 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]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2012-August/067297.html [2]UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2012-August/067298.html [3]FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067289.html [4]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067291.html [5]FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067288.html [6]FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-August/067290.html [7]FAILED winbot / zc_buildout_dev py_254_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-August/067308.html [8]FAILED winbot / zc_buildout_dev py_265_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-August/067309.html [9]FAILED winbot / zc_buildout_dev py_265_win32 master https://mail.zope.org/pipermail/zope-tests/2012-August/067307.html [10] FAILED winbot / zc_buildout_dev py_265_win64 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-August/067312.html [11] FAILED winbot / zc_buildout_dev py_265_win64 master https://mail.zope.org/pipermail/zope-tests/2012-August/067310.html [12] FAILED winbot / zc_buildout_dev py_270_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-August/067313.html [13] FAILED winbot / zc_buildout_dev py_270_win32 master https://mail.zope.org/pipermail/zope-tests/2012-August/067311.html [14] FAILED winbot / zc_buildout_dev py_270_win64 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-August/067315.html [15] FAILED winbot / zc_buildout_dev py_270_win64 master https://mail.zope.org/pipermail/zope-tests/2012-August/067314.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: 29, OK: 15
On Mon, Aug 27, 2012 at 03:26:28PM +0200, Adam GROSZER wrote: > Well, 3.4 KGS is not really interesting anymore, but it would be > pretty helpful to have the same individual packages tested somewhere > on linux as winbot does. > > Anyone? Ideas? Time? http://travis-ci.org/ ? 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: 29, OK: 15
On 08/27/2012 03:00 PM, Marius Gedminas wrote: On Mon, Aug 27, 2012 at 02:39:54PM +0300, Marius Gedminas wrote: The only buildbot I have access to is the one at http://zope3.pov.lt/. ... Something is wrong with one of the two buildslaves of the 3.4 KGS buildbot -- most likely Wake-on-LAN stopped working again, since I don't see any activity from it since Aug 10. I'll go kick it, but then again I don't think anybody cares about something as ancient as the Zope 3.4 KGS any more. That machine seems to be dead. There are currently no plans to replace it, so I guess that's the end of 32-bit Linux builds of the 3.4 KGS. Well, 3.4 KGS is not really interesting anymore, but it would be pretty helpful to have the same individual packages tested somewhere on linux as winbot does. Anyone? Ideas? Time? -- Best regards, Adam GROSZER -- Quote of the day: The 7 Modern Sins: Politics without principles, Pleasures without conscience, Wealth without work, Knowledge without character, Industry without morality, Science without humanity, Worship without sacrifice. - Canon Frederic Donaldson ___ 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: 29, OK: 15
On Mon, Aug 27, 2012 at 02:39:54PM +0300, Marius Gedminas wrote: > The only buildbot I have access to is the one at http://zope3.pov.lt/. ... > Something is wrong with one of the two buildslaves of the 3.4 KGS > buildbot -- most likely Wake-on-LAN stopped working again, since I don't > see any activity from it since Aug 10. I'll go kick it, but then again > I don't think anybody cares about something as ancient as the Zope 3.4 > KGS any more. That machine seems to be dead. There are currently no plans to replace it, so I guess that's the end of 32-bit Linux builds of the 3.4 KGS. Marius Gedminas -- Star Trek promised me computers I could talk to but what I got was a telephone I type on. -- "Sarcastro" 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] [ZODB-Dev] [announce] NEO 1.0 - scalable and redundant storage for ZODB
On Mon, Aug 27, 2012 at 2:37 PM, Vincent Pelletier wrote: > Hi, > > We've just tagged the 1.0 NEO release. > > NEO aims at being a replacement for use-cases where ZEO is used, but > with better scalability (by allowing data of a single database to be > distributed over several machines, and by removing database-level > locking), with failure resilience (by mirroring database content among > machines). Under the hood, it relies on simple features of SQL > databases (safe on-disk data structure, efficient memory usage, > efficient indexes). That sounds pretty cool! ___ 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] [announce] NEO 1.0 - scalable and redundant storage for ZODB
Hi, We've just tagged the 1.0 NEO release. NEO aims at being a replacement for use-cases where ZEO is used, but with better scalability (by allowing data of a single database to be distributed over several machines, and by removing database-level locking), with failure resilience (by mirroring database content among machines). Under the hood, it relies on simple features of SQL databases (safe on-disk data structure, efficient memory usage, efficient indexes). Release highlights: - production-ready ! - asynchronous replication across clusters, for inter-datacenter redundancy - there will be no further expensive data schema changes within the 1.x branch as there were in 0.x branch - replication performance is significantly increased - general implementation performance improved - several bugfixes What you need to know if you are used to ZODB features: - Blob API is not implemented yet. - pack's GC phase will not be implemented in NEO, it relies on zc.zodbdgc for this: http://pypi.python.org/pypi/zc.zodbdgc For more details, look at README and CHANGES included with the sources: http://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/README http://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/CHANGES NEO is published on pypi as "neoppod": http://pypi.python.org/pypi/neoppod Regards, -- Vincent Pelletier ERP5 - open source ERP/CRM for flexible enterprises ___ 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: 29, OK: 15
(I've trimmed the Cc: list) On Mon, Aug 27, 2012 at 12:22:51PM +0200, Patrick Gerken wrote: > @Christophe Combelles @Marius Gedminas > Both buildbots do not provide the xmlrpc interface any longer, do you > know why? Did you maybe upgrade and this xmlrpc interface is not > provided any longer? The only buildbot I have access to is the one at http://zope3.pov.lt/. I've recently upgraded the server from Ubuntu 10.04 to 12.04, which also means I upgraded buildbot from 0.7.12-1ubuntu1 to 0.8.5-2. This may have affected something or it may not, and I've no idea which two buildbots you're talking about. > Also, we are currently only getting E-Mails from the winbots and Epy, > so we only have windows tests and zope tests. No ztk or grok or > bluebream for linux. Something is wrong with one of the two buildslaves of the 3.4 KGS buildbot -- most likely Wake-on-LAN stopped working again, since I don't see any activity from it since Aug 10. I'll go kick it, but then again I don't think anybody cares about something as ancient as the Zope 3.4 KGS any more. Marius Gedminas -- 9. Okay, then, what do you think about "syntactic noise" in config files? !@#@!#(#%^!%$@#';,!@# -- http://alumnit.ca/wiki/index.php?page=RetchMail 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: 29, OK: 15
Most of these tests seem to be real failures. I was wondering why they do only provoke errors on the winbots, this resulted in more questions. @Christophe Combelles @Marius Gedminas Both buildbots do not provide the xmlrpc interface any longer, do you know why? Did you maybe upgrade and this xmlrpc interface is not provided any longer? Also, we are currently only getting E-Mails from the winbots and Epy, so we only have windows tests and zope tests. No ztk or grok or bluebream for linux. Is this intentional, should I remove the buildbots from the documentation or just a mistake? On Sat, Aug 25, 2012 at 3:00 AM, Zope tests summarizer wrote: > This is the summary for test reports received on the > zope-tests list between 2012-08-23 00:00:00 UTC and 2012-08-24 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-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 > [1]winbot / ZODB_dev py_265_win32 > [2]winbot / ZODB_dev py_265_win64 > [3]winbot / ZODB_dev py_270_win32 > [4]winbot / ZODB_dev py_270_win64 > [5]winbot / z3c.baseregistry_py_265_32 > [6]winbot / z3c.contents_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.formui_py_265_32 > [11] winbot / z3c.layer.pagelet_py_265_32 > [12] winbot / z3c.layer.ready2go_py_265_32 > [13] winbot / z3c.menu.ready2go_py_265_32 > [14] winbot / z3c.pagelet_py_265_32 > [15] winbot / z3c.pdftemplate_py_265_32 > [16] winbot / z3c.recipe.paster_py_265_32 > [17] winbot / z3c.rml_py_265_32 > [18] winbot / z3c.tabular_py_265_32 > [19] winbot / z3c.tabular_py_265_32 > [20] winbot / zc_buildout_dev py_254_win32 1.6.x > [21] winbot / zc_buildout_dev py_265_win32 1.6.x > [22] winbot / zc_buildout_dev py_265_win32 master > [23] winbot / zc_buildout_dev py_265_win64 1.6.x > [24] winbot / zc_buildout_dev py_265_win64 master > [25] winbot / zc_buildout_dev py_270_win32 1.6.x > [26] winbot / zc_buildout_dev py_270_win32 master > [27] winbot / zc_buildout_dev py_270_win64 1.6.x > [28] winbot / zc_buildout_dev py_270_win64 master > [29] winbot / zope.app.twisted_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 / ZODB_dev py_265_win32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067180.html > > > [2]FAILED winbot / ZODB_dev py_265_win64 >https://mail.zope.org/pipermail/zope-tests/2012-August/067137.html > > > [3]FAILED winbot / ZODB_dev py_270_win32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067138.html > > > [4]FAILED winbot / ZODB_dev py_270_win64 >https://mail.zope.org/pipermail/zope-tests/2012-August/067139.html > > > [5]FAILED winbot / z3c.baseregistry_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067140.html > > > [6]FAILED winbot / z3c.contents_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067162.html > > > [7]FAILED winbot / z3c.contents_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067142.html > > > [8]FAILED winbot / z3c.coverage_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067147.html > > > [9]FAILED winbot / z3c.datagenerator_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067151.html > > > [10] FAILED winbot / z3c.formui_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067153.html > > > [11] FAILED winbot / z3c.layer.pagelet_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067150.html > > > [12] FAILED winbot / z3c.layer.ready2go_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067145.html > > > [13] FAILED winbot / z3c.menu.ready2go_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067152.html > > > [14] FAILED winbot / z3c.pagelet_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067148.html > > > [15] FAILED winbot / z3c.pdftemplate_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2012-August/067146.html > > > [16] FAILED winbot / z3c.recipe