-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
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
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
-
-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 :
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
