This is the summary for test reports received on the zope-tests list between 2013-09-11 00:00:00 UTC and 2013-09-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 ---------------- [1] winbot / z3c.ptcompat_py_265_32 [2] winbot / zope.app.authentication_py_265_32 [3] winbot / zope.app.http_py_265_32 [4] winbot / zope.app.publication_py_265_32 [5] winbot / zope.app.publisher_py_265_32 [6] winbot / zope.app.security_py_265_32 [7] winbot / zope.app.session_py_265_32 [8] winbot / zope.app.wsgi_py_265_32 [9] winbot / zope.catalog_py_265_32 [10] winbot / zope.exceptions_py_265_32 [11] winbot / zope.session_py_265_32 [12] winbot / zope.viewlet_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 / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078710.html [2] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078701.html [3] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078702.html [4] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078700.html [5] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078704.html [6] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078707.html [7] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078708.html [8] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078703.html [9] FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078709.html [10] FAILED winbot / zope.exceptions_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078711.html [11] FAILED winbot / zope.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078706.html [12] FAILED winbot / zope.viewlet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078705.html
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1] winbot / z3c.ptcompat_py_265_32 [5] winbot / zope.app.publisher_py_265_32 [6] winbot / zope.app.security_py_265_32 [7] winbot / zope.app.session_py_265_32 [9] winbot / zope.catalog_py_265_32 [10] winbot / zope.exceptions_py_265_32 [11] winbot / zope.session_py_265_32 [12] winbot / zope.viewlet_py_265_32
GitHub was unreachable: fatal: unable to connect to github.com: github.com[0: 192.30.252.130]: errno=No such file or directory Ironically, https://status.github.com/ is giving me a 500 Internal Server Error right now. <a few minutes later> It's back up and shows no downtime during the last 7 days. Must be a network problem.
[2] winbot / zope.app.authentication_py_265_32 [3] winbot / zope.app.http_py_265_32 [4] winbot / zope.app.publication_py_265_32 [8] winbot / zope.app.wsgi_py_265_32
zope.testbrowser-caused WebTest version conflict. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[2] winbot / zope.app.authentication_py_265_32 [3] winbot / zope.app.http_py_265_32 [4] winbot / zope.app.publication_py_265_32 [8] winbot / zope.app.wsgi_py_265_32
zope.testbrowser-caused WebTest version conflict.
I've no idea why these errors disappeared.
I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do).
I basically chickened out. IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package). What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (<=4.x) to newer versions (5.x). I will not do a release until this documentation exists. It may take me some time to find the time and remember how everything fits together. It shouldn't be too hard (just find some zope package that did the migration in a py3 branch, then document what it did), but I find my motivation is pretty low this week. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On 09/23/2013 10:03 AM, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[2] winbot / zope.app.authentication_py_265_32 [3] winbot / zope.app.http_py_265_32 [4] winbot / zope.app.publication_py_265_32 [8] winbot / zope.app.wsgi_py_265_32
zope.testbrowser-caused WebTest version conflict.
I've no idea why these errors disappeared.
I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do).
I basically chickened out.
IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package).
What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (<=4.x) to newer versions (5.x).
I will not do a release until this documentation exists.
Could you add a line to let's say CHANGES.txt about this? The idea would be to really block a release. Not that someone comes around and pushes the release out half baked. -- Best regards, Adam GROSZER -- Quote of the day: It is never worthwhile to make rents in a garment for the sake of mending them? Nor to create doubts in order to show how cleverly we can quiet them. - Charles Haddon Spurgeon
participants (3)
-
Adam GROSZER -
Marius Gedminas -
Zope tests summarizer