buildbot for ZTK released packages (linux 32)
It's live again. This one tests only released packages: http://buildbot.afpy.org/ztk1.0/waterfall Failures : python2.4 : zope - zope.browserpage - zope.viewlet - zope.contentprovider - zope.defferedimport - zope.app.wsgi python 2.5 and 2.6 : - zope.app.wsgi python2.7b2 : - zope.testing - zope.formlib - zope.proxy - zope.exceptions - zope.app.publisher - zope.app.wsgi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christophe Combelles wrote:
It's live again. This one tests only released packages:
Great! That should induce us to stay on the ball about making releases for 'fixcommitted' bugs.
http://buildbot.afpy.org/ztk1.0/waterfall
Failures :
python2.4 : zope - zope.browserpage - zope.viewlet - zope.contentprovider - zope.defferedimport - zope.app.wsgi
python 2.5 and 2.6 : - zope.app.wsgi
I plan to work on fixing this failure, which is due to moving the zope.testbrowser pin from 3.8.2 to 3,9.1.
python2.7b2 : - zope.testing - zope.formlib - zope.proxy - zope.exceptions - zope.app.publisher - zope.app.wsgi
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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvz9NYACgkQ+gerLs4ltQ4wkgCfWYpnYHT4mkwWUIwRF4l7h12U 6M0An1a1jvDDbz08yxyL2ZZr3SkroM/k =PeYS -----END PGP SIGNATURE-----
Tres Seaver wrote:
python 2.5 and 2.6 : - zope.app.wsgi
I plan to work on fixing this failure, which is due to moving the zope.testbrowser pin from 3.8.2 to 3,9.1.
How are you going to fix it? I'm asking because we depend on zope.app.wsgi for the browser testing of Grok now, at least on a branch. Regards, Martijn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote:
Tres Seaver wrote:
python 2.5 and 2.6 : - zope.app.wsgi I plan to work on fixing this failure, which is due to moving the zope.testbrowser pin from 3.8.2 to 3,9.1.
How are you going to fix it? I'm asking because we depend on zope.app.wsgi for the browser testing of Grok now, at least on a branch.
I don't know yet -- I planned to look at the failure more closely, and figure out something that would work with the newer mechanize. 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv0DTUACgkQ+gerLs4ltQ6rUgCePwYHmyagITfQ380VNoPzg6D4 L2oAmwQIxeajJwf17DudE0H8RND9mgxB =/Z10 -----END PGP SIGNATURE-----
Tres Seaver wrote:
I don't know yet -- I planned to look at the failure more closely, and figure out something that would work with the newer mechanize.
Just for your information, what we're doing is using wsgi_intercept, which hooks into zope.testbrowser, which uses mechanize. But I think we actually need more tests for it in zope.app.wsgi. Anyway, let me know if you need any help on this. Regards, Martijn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote:
Tres Seaver wrote:
I don't know yet -- I planned to look at the failure more closely, and figure out something that would work with the newer mechanize.
Just for your information, what we're doing is using wsgi_intercept, which hooks into zope.testbrowser, which uses mechanize. But I think we actually need more tests for it in zope.app.wsgi.
Anyway, let me know if you need any help on this.
Basically, the new mechanize neither needs nor wants to have the '_http_upgrade_response' key lying around: I fixed the zope.app.wsgi tests by removing it. All the zopeapp tests now pass for me, with that one egg in development mode. If you (or some other Grok developer) can confirm that the zope.app.wsgi trunk still works for your tests, I will release a new version and bump the ZTK config to include it. 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv4I/IACgkQ+gerLs4ltQ6AKQCdGlt1iATNroCCLkyBGmvyxOOq OIsAn2/PCGxe5mg5LsNO2QCG3VekyGxB =7U+v -----END PGP SIGNATURE-----
Hi there, Tres Seaver wrote:
Martijn Faassen wrote:
Tres Seaver wrote:
I don't know yet -- I planned to look at the failure more closely, and figure out something that would work with the newer mechanize.
Just for your information, what we're doing is using wsgi_intercept, which hooks into zope.testbrowser, which uses mechanize. But I think we actually need more tests for it in zope.app.wsgi.
Anyway, let me know if you need any help on this.
Basically, the new mechanize neither needs nor wants to have the '_http_upgrade_response' key lying around: I fixed the zope.app.wsgi tests by removing it. All the zopeapp tests now pass for me, with that one egg in development mode.
If you (or some other Grok developer) can confirm that the zope.app.wsgi trunk still works for your tests, I will release a new version and bump the ZTK config to include it.
All groktoolkit grok tests (opposed to ecosphere tests) pass as well for me with the fixed z.a.wsgi trunk in development mode. The failures in groktoolkit ecosphere tests seem not to be related to the change in z.a.wsgi but already happened before and for different reasons. AFAICS the change is okay for grok packages. Thanks for fixing this! -- Uli
participants (4)
-
Christophe Combelles -
Martijn Faassen -
Tres Seaver -
Uli Fouquet