Re: [Zope-dev] SVN: DateTime/trunk/ Moved to GitHub.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/25/2013 01:18 AM, Stephen Richter wrote: Premature. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEraxMACgkQ+gerLs4ltQ4kMwCgrOtFjTc3/ToGcLAmsRnZI1hB 8/0AoIP2T8BEoHEHlu7oKpkkWpJHRwOd =E33A -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 )
[Zope-dev] zope-tests - FAILED: 21, OK: 19
This is the summary for test reports received on the zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-25 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 # 184 [2]Still Failing - zopetoolkit_trunk_app - Build # 166 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 [3]winbot / z3c.authenticator_py_265_32 [4]winbot / z3c.authenticator_py_265_32 [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 [11] winbot / z3c.layer.ready2go_py_265_32 [12] winbot / z3c.layer.ready2go_py_265_32 [13] winbot / z3c.recipe.paster_py_265_32 [14] winbot / zope.app.authentication_py_265_32 [15] winbot / zope.app.pagetemplate_py_265_32 [16] winbot / zope.app.wsgi_py_265_32 [17] winbot / zope.app.wsgi_py_265_32 [18] winbot / zope.browserpage_py_265_32 [19] winbot / zope.browserpage_py_265_32 [20] winbot / zope.sendmail_py_265_32 [21] winbot / zope.structuredtext_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 # 184 https://mail.zope.org/pipermail/zope-tests/2013-February/072810.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 166 https://mail.zope.org/pipermail/zope-tests/2013-February/072811.html [3]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072833.html [4]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072799.html [5]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072834.html [6]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072797.html [7]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072806.html [8]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072809.html [9]FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072805.html [10] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072807.html [11] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072836.html [12] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072802.html [13] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072831.html [14] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072803.html [15] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072808.html [16] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072832.html [17] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072798.html [18] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072835.html [19] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072800.html [20] FAILED winbot / zope.sendmail_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072801.html [21] FAILED winbot / zope.structuredtext_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072804.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
Re: [Zope-dev] zope-tests - FAILED: 21, OK: 19
On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-25 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 # 184
IOError: [Errno 2] No such file or directory:
'/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi/setup.py'
I see two other zope.app packages also moved to Github:
zope.app.http
zope.app.appsetup
I've updated all three in zopeapp-sources.cfg.
[2]Still Failing - zopetoolkit_trunk_app - Build # 166
Same.
[3]winbot / z3c.authenticator_py_265_32
[4]winbot / z3c.authenticator_py_265_32
There's an echo? Anyway, same old
Failed example:
p.password
Expected:
u'secret'
Got:
'secret'
and I'd fix it if I knew whether passwords ought to be unicode or byte
strings.
[5]winbot / z3c.contents_py_265_32
[6]winbot / z3c.contents_py_265_32
There's this lovely bit at the beginning I don't remember from before,
but it's not counted as a test failure:
ZopeXMLConfigurationError: File
c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line
41.2-41.32
ZopeXMLConfigurationError: File
c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51
WindowsError: [Error 3] The system cannot find the path specified:
u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*'
and then we have the form id name vs form name id in README.txt that
I cannot reproduce.
[7]winbot / z3c.form_py_265_32
Winbot failed to build lxml:
Getting distribution for 'lxml==3.1.0'.
Building lxml version 3.1.0.
Building without Cython.
ERROR: 'xslt-config' is not recognized as an internal or external command,
operable program or batch file.
** make sure the development packages of libxml2 and libxslt are installed
**
...
c:\temp\easy_install-tgshvo\lxml-3.1.0\src\lxml\includes\etree_defs.h(9)
: fatal error C1083: Cannot open include file:
'libxml/xmlversion.h': No such file or directory
[8]winbot / z3c.formui_py_265_32
Same: no lxml.
[9]winbot / z3c.jsonrpc_py_265_32
[10] winbot / z3c.jsontree_py_265_32
Same old Invalid request id returned.
[11] winbot / z3c.layer.ready2go_py_265_32
[12] winbot / z3c.layer.ready2go_py_265_32
ZopeXMLConfigurationError: File
c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\ftesting.zcml,
line 62.2-62.32
ZopeXMLConfigurationError: File
c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51
WindowsError: [Error 3] The system cannot find the path specified:
u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*'
Okay, this does cause a test failure. Scratch that, a layer setup
failure.
Broken z3c.form release that's missing some locales? Some packages have
special build steps (compile *.mo or something) before you're supposed
to do setup.py sdist register upload.
[13] winbot / z3c.recipe.paster_py_265_32
Error: Couldn't find a distribution for 'beautifulsoup4'.
Pulled in by WebTest 2.0, which is pulled in by zope.app.wsgi 3.15.0.
WebTest also pulls in waitress.
These two packages need to be explicitly made available to the test
environment.
[14] winbot / zope.app.authentication_py_265_32
File
c:\buildslave\zope.app.authentication\build\src\zope\app\authentication\principalfolder.txt,
line 28, in principalfolder.txt
Failed example:
principals.authenticateCredentials({'login': 'login1', 'password': '123'})
Expected:
PrincipalInfo(u'principal.p1')
Got:
PrincipalInfo('principal.p1')
and similar.
[15] winbot / zope.app.pagetemplate_py_265_32
Same old AssertionError: u'42\r\n' != '42\n'
[16] winbot / zope.app.wsgi_py_265_32
[17] winbot / zope.app.wsgi_py_265_32
Same old PEP- violation.
[18] winbot / zope.browserpage_py_265_32
[19] winbot / zope.browserpage_py_265_32
My guess would be extra \r's in output, because look:
Failed example:
print(MyView(MyContent('bob'), TestRequest())(x=42))
Expected:
htmlbody
Hello bob
The URL is http://127.0.0.1
The positional arguments were ()
The keyword argument x is 42
/body/html
BLANKLINE
Got:
htmlbody
Hello bob
The URL is http://127.0.0.1
The positional arguments were ()
The keyword argument x is 42
/body/html
BLANKLINE
Also other tests fail like this
AssertionError: 'htmlbodypdone/p/body/html\r\n' !=
'htmlbodypdone/p/body/html\n'
[20] winbot / zope.sendmail_py_265_32
[21] winbot / zope.structuredtext_py_265_32
All tests pass in latest build
Marius Gedminas
--
http://pov.lt/
