zope-tests - FAILED: 4, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-06 00:00:00 UTC and 2013-09-07 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 / zope.app.authentication_py_265_32 [2] winbot / zope.app.http_py_265_32 [3] winbot / zope.app.publication_py_265_32 [4] winbot / zope.app.wsgi_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 / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html
[3] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html
[4] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase: - -------------------- %< ----------------------- c:\buildslave\zope.app.wsgi\build>call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat" x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 - -------------------- %< ----------------------- Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlIrxFgACgkQ+gerLs4ltQ4R+QCfTmElgT9bLTKi//6JtRWoZ17S +l8An2nWUfe7sGMijMkDqSAVIeMH5A6/ =E0GF -----END PGP SIGNATURE-----
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html
[3] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html
[4] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase:
-------------------- %< ----------------------- c:\buildslave\zope.app.wsgi\build>call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat" x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 -------------------- %< -----------------------
Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest <= 1.3.4']. OTOH it wasn't me who added that <= constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7... I just made a release with all the accumulated changes. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2] FAILED winbot / zope.app.http_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html
[3] FAILED winbot / zope.app.publication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html
[4] FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase:
-------------------- %< ----------------------- c:\buildslave\zope.app.wsgi\build>call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat" x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 -------------------- %< -----------------------
Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest <= 1.3.4'].
OTOH it wasn't me who added that <= constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7...
I just made a release with all the accumulated changes.
Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlIt9rkACgkQ+gerLs4ltQ4G+ACeJA6XZdZzR0EXWWWuiHAGJNTY TPQAnAgR9Uj3L1IqT5a1+sLrDugHAF8c =vHtg -----END PGP SIGNATURE-----
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote:
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase:
-------------------- %< ----------------------- While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 -------------------- %< -----------------------
Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest <= 1.3.4'].
OTOH it wasn't me who added that <= constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7...
I just made a release with all the accumulated changes.
Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest?
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.) Andrey? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote:
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase:
-------------------- %< ----------------------- While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 -------------------- %< -----------------------
Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest <= 1.3.4'].
OTOH it wasn't me who added that <= constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7...
I just made a release with all the accumulated changes.
Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest?
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.)
Indeed, and it's had no changes for at least 5 months and been tested with a few existing codebases. +1 for releasing it
Andrey?
Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
_______________________________________________ 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 )
-- Brian Sutherland
On Tue, Sep 10, 2013 at 09:49:50AM +0200, Brian Sutherland wrote:
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.)
Indeed, and it's had no changes for at least 5 months and been tested with a few existing codebases.
+1 for releasing it
One tests fails in the py3 branch: test_strip_linebreaks_from_textarea. It tests that if you inspect getControl(name='textarea').value, you'll see one initial '\n' stripped away. This fails when the textarea in question has two initial newlines: <textarea> Foo </textarea> The test expects .value to be '\nFoo\n', but it actually gets 'Foo\n'. This test was added by Benji York in 2006 (commit 4545f144) and refers to "issue 644" in some unspecified bug tracker. Google allowed me to find a copy of the issue in question: https://bugs.launchpad.net/zope3/+bug/98371 In particular the following comment is interesting: "We've verified that browsers (we tested Firefox, Mozilla, Safari, and IE) will strip a single leading newline (crlf) if it is at the beginning of the string." -- Jim Fulton, https://bugs.launchpad.net/zope3/+bug/98371/comments/12 It was serious enough to warrant changes to the local copy of ClientForm (and an upstream submission of the patch). It looks like what happened here was that WebTest itself was modified to eat the first newline in a textarea: https://github.com/Pylons/webtest/pull/69 so now we eat two. This change was released in WebTest 2.0.6: http://webtest.pythonpaste.org/en/latest/changelog.html#id2 I guess what we have to do is remove the 1st newline stripping logic from zope.testbrowser and require WebTest >= 2.0.6. Ok, fixed. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.)
I think I remembered now: a WebTest release with some bugfixes. I'm trying to merge the py3 branch to master now. There's one issue: the test for https://github.com/zopefoundation/zope.testbrowser/pull/4 uses the internal .mech_browser attribute. I think what is actually wanted here is a new API: browser.handleRedirects = False browser.open(...) # or browser.submit() assert browser.getHeaders('Status') == '302 Found' Comments? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Thursday, September 12, 2013 11:38:16 AM Marius Gedminas wrote:
m trying to merge the py3 branch to master now. There's one issue: the test for https://github.com/zopefoundation/zope.testbrowser/pull/4 uses the internal .mech_browser attribute.
I think what is actually wanted here is a new API:
browser.handleRedirects = False browser.open(...) # or browser.submit() assert browser.getHeaders('Status') == '302 Found'
Comments?
+1 That looks good. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
participants (5)
-
Brian Sutherland -
Marius Gedminas -
Stephan Richter -
Tres Seaver -
Zope tests summarizer