-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zope Tests Summarizer wrote:
> Summary of messages to the zope-tests list.
> Period Sun Dec 7 12:00:00 2008 UTC to Mon Dec 8 12:00:00 2008 UTC.
> There were 6 messages: 6 from Zope Tests.
>
>
> Test failures
> -------------
>
> Subject: FAILED (failures=7) : Zope-2.11 Python-2.4.5 : Linux
> From: Zope Tests
> Date: Sun Dec 7 20:29:11 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010612.html
I have fixed this one as follows:
- I upgraded the mechanize external to the vendor-imported 0.10
version.
- I upgraded the 'zope.testbrowser' external to the Zope2-specific
version which suppresses the 'over-the-wire.txt' tests (which should
*never* run automatically, BTW).
- I updated 'Products.Five.testbrowser' to strip out the '_seek'
handler, which was never part of the relased version of 'mechanize'
on which our internal fork was based.
> Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
> From: Zope Tests
> Date: Sun Dec 7 20:30:42 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010613.html
>
> Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux
> From: Zope Tests
> Date: Sun Dec 7 20:32:12 EST 2008
> URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010614.html
For the trunk I have spelunked the 'zope.testbrowser' failure, which is
due to a difference between Zope2 and Zope3 requests: the Z3 versions
have empty 'processInputs' methods, while the Z2 version drains the
input stream for non-GET methods, creating a cgi.FieldStorage. I would
just as soon disable the test under Zope2 (e.g., with something like the
attached patch), rather than care about the different semantics. I
could create another Z2-specific tag for this, if needed.
I still don't have a clue why the 'aqlegacy_ftest.txt' tests fail. Ideas?
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJPVT9+gerLs4ltQ4RAgWBAJ9VSV1vaC32Mj3EIy+fy8SpszLnJACeL+Pp
sjhqfFsU6QDQ4dyZuSGDzbc=
=Ecve
-----END PGP SIGNATURE-----
Index: zope/testbrowser/tests.py
===================================================================
--- zope/testbrowser/tests.py (revision 93787)
+++ zope/testbrowser/tests.py (working copy)
@@ -391,6 +391,14 @@
def test_suite():
flags = doctest.NORMALIZE_WHITESPACE | doctest.ELLIPSIS
+ try:
+ # The doctests make Zope3-specifc assumptions about how the
+ # publisher works; skip them if running inside a Zope2 environment
+ import ZPublisher
+ except ImportError:
+ pass
+ else:
+ return unittest.TestSuite()
readme = FunctionalDocFileSuite('README.txt', optionflags=flags,
checker=checker)
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
