The tests are failing on the trunk, 3.2, and 3.3 branches. Apparently
because of the recent addition of a "Cache-Control" header. See the
buildbot for details: http://buildbot.zope.org
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky Burt wrote:
> On Wed, 2007-10-01 at 11:09 -0500, Tres Seaver wrote:
>> While I am vehemently opposed to code generation per se, one alternative
>> which I think is important is to generate stuff *at runtime* from
>> artifacts which are more under
On Wed, 2007-10-01 at 11:09 -0500, Tres Seaver wrote:
> While I am vehemently opposed to code generation per se, one alternative
> which I think is important is to generate stuff *at runtime* from
> artifacts which are more understandable to business users than Python
> code. E.g., they might spec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
> Am Mittwoch, den 10.01.2007, 11:04 -0500 schrieb Benji York:
>> Christian Theune wrote:
>>> I propose to add an "ultimate" pop at the beginning of each test, to
>>> ensure consistency/isolation at those points.
>> Where "ultim
Am Mittwoch, den 10.01.2007, 11:04 -0500 schrieb Benji York:
> Christian Theune wrote:
> > I propose to add an "ultimate" pop at the beginning of each test, to
> > ensure consistency/isolation at those points.
>
> Where "ultimate pop" means to remove all stacked demostorages added by
> previous t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Martin Aspeli wrote:
>> Peter Bengtsson wrote:
Philipp has posted a blog entry with a good example of Grok code:
http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn
Christian Theune wrote:
I propose to add an "ultimate" pop at the beginning of each test, to
ensure consistency/isolation at those points.
Where "ultimate pop" means to remove all stacked demostorages added by
previous tests? If so, sounds good.
I do worry a little about that hiding mismatc
Philipp von Weitershausen wrote:
Martijn Faassen wrote:
- Don't invent a new code generator. Please. :) PasteScript does
quite well, and seems to be adopted by others, e.g. Pylons. We
already use it to make new egg-like packages for Plone.
Agreed. We're looking into PasteScript, I believe. P
Martijn Faassen wrote:
- Don't invent a new code generator. Please. :) PasteScript does
quite well, and seems to be adopted by others, e.g. Pylons. We already
use it to make new egg-like packages for Plone.
Agreed. We're looking into PasteScript, I believe. Philipp has been
looking into this
Christian Theune a écrit :
> Hi,
>
> after the initial Zope 3.3 release, we fixed quite a few bugs. I think
> it's time for a 3.3.1 release now, which would also help the upcoming
> Zope 2.10.2 release.
>
> If anybody has time to do the 3.3.1 release, that would be very welcome!
Hi, that would b
Hi,
after the initial Zope 3.3 release, we fixed quite a few bugs. I think
it's time for a 3.3.1 release now, which would also help the upcoming
Zope 2.10.2 release.
If anybody has time to do the 3.3.1 release, that would be very welcome!
Christian
--
gocept gmbh & co. kg - forsterstraße 29 -
Christian Theune wrote:
Hi,
I'd like to propose a change to zc.selenium to increase test isolation
in the face of failing tests.
We use demostorage elegantly by keeping a stack of wrapped storages that
are pushed and popped automatically while the selenium tests run.
However, when a test fails
Martin Aspeli wrote:
Peter Bengtsson wrote:
Philipp has posted a blog entry with a good example of Grok code:
http://www.z3lab.org/sections/blogs/philipp-weitershausen/2007_01_09_you-thought-zope-3-wasn
Gorgeous!
I especially like that you don't have to manually define the template
since it
Hello Christian,
Yay, shame on me.
I was the one who added the "no cache" stuff to
/src/zope/app/exception/browser/unauthorized.py.
I'm crippled here until tomorrow without SVN access, so somebody
please fix it or revert my changes.
Wednesday, January 10, 2007, 11:00:35 AM, you wrote:
CT> Hi,
Hi,
I'd like to propose a change to zc.selenium to increase test isolation
in the face of failing tests.
We use demostorage elegantly by keeping a stack of wrapped storages that
are pushed and popped automatically while the selenium tests run.
However, when a test fails, selenium might skip a fe
Hi,
that one fails for me as well.
I don't remember who checked this in, but I saw somebody talk about this
change lately.
Christian
Am Mittwoch, den 10.01.2007, 10:31 +0530 schrieb Baiju M:
> Baiju M wrote:
> > Hi, Can anyone verify that buildbot [1] send test failure error mails
> > to list
Hi,
Am Mittwoch, den 10.01.2007, 00:44 + schrieb Martin Aspeli:
> Code generation sucks. :)
>
> But:
>
> - ArchGenXML (hacky though it is) is great for business types because
> it takes UML (which business analysts understand and customers can be
> talked through) and produces content ty
17 matches
Mail list logo
