zope-tests - FAILED: 5, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-18 00:00:00 UTC and 2013-03-19 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] Still Failing - zopetoolkit_trunk - Build # 207 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 / z3c.form_py_265_32 [3] winbot / z3c.formui_py_265_32 [4] winbot / z3c.layer.ready2go_py_265_32 [5] winbot / z3c.pagelet_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 Still Failing - zopetoolkit_trunk - Build # 207 https://mail.zope.org/pipermail/zope-tests/2013-March/073425.html [2] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073421.html [3] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073424.html [4] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073422.html [5] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073423.html
On Wed, Mar 20, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 207
Same four persistent import errors. Back in February I thought these were caused by an incorrect setup.py in ZODB. That's been fixed, yet the errors persist. And I can't reproduce them using upstream master checkouts of, e.g., zope.container or zope.traversal.
[2] winbot / z3c.form_py_265_32
We're out of the lxml swamp and get exciting new failures! \r\n instead of \n
[3] winbot / z3c.formui_py_265_32
Network error while fetching distribute during bootstrap. Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache.
[4] winbot / z3c.layer.ready2go_py_265_32 [5] winbot / z3c.pagelet_py_265_32
Last builds succeeded for both! Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On 03/20/2013 07:27 AM, Marius Gedminas wrote:
[3] winbot / z3c.formui_py_265_32
Network error while fetching distribute during bootstrap.
Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache.
pypi distribute download count is at *510000*, and that's just the latest version. btw, I think earlier bootstraps too download setuptools/distribute ignoring the buildout cache. https://github.com/buildout/buildout/issues/107 -- Best regards, Adam GROSZER -- Quote of the day: I've made such a terrible mess of things... and all I wanted to do was rule the universe. - Unknown
On Wed, Mar 20, 2013 at 08:30:27AM +0100, Adam GROSZER wrote:
On 03/20/2013 07:27 AM, Marius Gedminas wrote:
[3] winbot / z3c.formui_py_265_32
Network error while fetching distribute during bootstrap.
Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache.
pypi distribute download count is at *510000*, and that's just the latest version. btw, I think earlier bootstraps too download setuptools/distribute ignoring the buildout cache.
I have the recollection that earlier bootstraps always used my /usr/lib/python2.7/dist-packages/setuptools, while the new bootstrap always downloads (and then likes to "upgrade" from bootstrap-downloaded 0.6.35 to 0.6.28 from /usr/lib/python2.7 on the next bin/buildout run, unless you run it with -n or -o). Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Wed, Mar 20, 2013 at 08:27:58AM +0200, Marius Gedminas wrote:
On Wed, Mar 20, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 207
Same four persistent import errors.
Back in February I thought these were caused by an incorrect setup.py in ZODB. That's been fixed, yet the errors persist. And I can't reproduce them using upstream master checkouts of, e.g., zope.container or zope.traversal.
I cannot reproduce these from a zopetoolkit checkout either.
[2] winbot / z3c.form_py_265_32
We're out of the lxml swamp and get exciting new failures!
\r\n instead of \n
Fixed.
[3] winbot / z3c.formui_py_265_32
Network error while fetching distribute during bootstrap.
Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache.
Checked for similar \r\n issues, found none. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Adam GROSZER -
Marius Gedminas -
Zope tests summarizer