This is the summary for test reports received on the zope-tests list between 2013-02-07 00:00:00 UTC and 2013-02-08 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 ---------------- Successful - zopetoolkit_trunk - Build # 166 Successful - zopetoolkit_trunk_app - Build # 149 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 / z3c.recipe.paster_py_265_32 [2] winbot / zope.app.schema_py_265_32 [3] winbot / zope.tal_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.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072019.html [2] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072021.html [3] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072020.html
On Sat, Feb 09, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[2] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072021.html
Not my fault this time! :-) Network error while talking to PyPI in the bootstrap step.
[3] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072020.html
Oh dear, http://zope3.pov.lt/trac/changeset/129235 was not enough to make all of the problem go away. I get the impression that using tal:repeat somehow produces a \r\r\n on one of the lines. The least bad thing about this is that I can reproduce the bug if I use wine c:/python27/python27.exe to bootstrap a buildout, and convert the test files to DOS line endings. People who care about Windows are invited to help out figure out what's the sensible thing for zope.tal to do. Complication: the XML parser used by zope.tal only works with byte strings on Python 3, and open(filename 'rb') doesn't do newline conversions. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Sat, Feb 09, 2013 at 12:31:27PM +0200, Marius Gedminas wrote:
On Sat, Feb 09, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[3] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072020.html
Oh dear, http://zope3.pov.lt/trac/changeset/129235 was not enough to make all of the problem go away. I get the impression that using tal:repeat somehow produces a \r\r\n on one of the lines.
Yes, it's a \r\r\n.
The least bad thing about this is that I can reproduce the bug if I use wine c:/python27/python27.exe to bootstrap a buildout, and convert the test files to DOS line endings.
No need for wine, this reproduces nicely on Linux, as long as I convert the files to DOS line endings.
People who care about Windows are invited to help out figure out what's the sensible thing for zope.tal to do.
I'm guessing \r\r\n in the output is undesirable.
Complication: the XML parser used by zope.tal only works with byte strings on Python 3, and open(filename 'rb') doesn't do newline conversions.
Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer