The problem is that when I do:
bin/zopectl test -s AccessControl
everything works fine.
However the buildbots do:
python test.py -s AccessControl
and this fails.
I included a workaround, sigh.
Florent
Stefan H. Holek wrote:
AFAIK the default configuration used by tests does not have a
Summary of messages to the zope-tests list.
Period Sun Jan 15 12:01:02 2006 UTC to Mon Jan 16 12:01:02 2006 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Test failures
-
Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux
From: Zope Unit Tests
Date: Sun Jan 15 21:10:28 EST
Hi,
While seaching for objects of all types containing some text through the
ZMI find tab, I got the traceback hereunder. (Zope 2.7.8-final on
windows)
Traceback (innermost last):
Module ZPublisher.Publish, line 101, in publish
Module ZPublisher.mapply, line 88, in mapply
Module
Hi,
Em Seg, 2006-01-16 às 16:20 +0100, Godefroid Chapelle escreveu:
Hi,
While seaching for objects of all types containing some text through the
ZMI find tab, I got the traceback hereunder. (Zope 2.7.8-final on
windows)
Traceback (innermost last):
[...]
Module OFS.Image, line
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2775
Blamelist: efge,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope-Dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've noticed a couple of problems with recent deprecation decisions (for
OFS.content_types and zLOG). The major one is that the deprecation
warning waw added without removing the code in the core which depends on
the deprecated feature. The most
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've noticed a couple of problems with recent deprecation decisions (for
OFS.content_types and zLOG). The major one is that the deprecation
warning waw added without removing the code in the core which depends on
the deprecated
--On 16. Januar 2006 13:08:31 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
I'll just note that:
- I agree with your point about deprecation warnings. IOW
we should not check in new deprecation warnings on the trunk
that cause warnings to be output when running the standard tests.
We
Andreas Jung wrote:
--On 16. Januar 2006 13:08:31 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
I'll just note that:
- I agree with your point about deprecation warnings. IOW
we should not check in new deprecation warnings on the trunk
that cause warnings to be output when running the
--On 16. Januar 2006 13:36:32 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
There are two separate issues here:
1. ZPT backward compatibility.
Are we introdcuting ZPT backward incompatibilities? (Aside from module
paths)?
My original implementation would introduce incompatibilities
10 matches
Mail list logo