This is the summary for test reports received on the
zope-tests list between 2011-10-25 00:00:00 UTC and 2011-10-26 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
On Wed, Oct 26, 2011 at 10:26 AM, Wolfgang Schnerring wrote:
> Hello,
>
> I've added an assertion helper to zope.testbrowser that provides
> ``assertEllipsis``, which is very helpful when using Testbrowser with
> unittest.TestCase (instead of doctests).
I'm +1 on the functionality, and -0 on the
Hello,
I've added an assertion helper to zope.testbrowser that provides
``assertEllipsis``, which is very helpful when using Testbrowser with
unittest.TestCase (instead of doctests).
Some examples:
self.assertEllipsis('...bar...', 'foo bar qux')
# -> nothing happens
self.assertEllipsis('foo',
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/26/2011 06:54 AM, Christophe Combelles wrote:
> Le 26/10/2011 03:57, Tres Seaver a écrit :
>> This run has the same two failures, plus the command-line error
>> for the 'cProfile' option. Christophe, can you please verify
>> that the Python 2.6
Le 26/10/2011 03:57, Tres Seaver a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Woohoo -- down to just seven!
>
>
>> [1]FAILED ZTK 1.1 / Python2.5.5 Linux 64bit
>> https://mail.zope.org/pipermail/zope-tests/2011-October/051688.html
>
> This
>>
> has the "sub-process buffer" fa
On Wed, Oct 26, 2011 at 3:57 AM, Tres Seaver wrote:
>> [6] FAILED winbot / z3c.form_py_265_32
>> https://mail.zope.org/pipermail/zope-tests/2011-October/051704.html
>
> I'm ignoring this one, except to note that it is *not* lxml related.
This was a version conflict for some Chameleon librarie
