On Sun, Nov 13, 2011 at 08:22:38AM -0500, Tres Seaver wrote:
> > [8]FAILED winbot / z3c.form_py_265_32
> > https://mail.zope.org/pipermail/zope-tests/2011-November/052551.html
>
> Stephan said yesterday he thought this was a chameleon bug. I just
> tried to reproduce this on a Linux box wit
Le 14/11/2011 01:52, Christophe Combelles a écrit :
> Le 13/11/2011 14:22, Tres Seaver a écrit :
>>> [1]FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit
>>> https://mail.zope.org/pipermail/zope-tests/2011-November/052554.html
>>
>> This is the same hour-long timeout as yesterday in the buildout ste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/14/2011 04:50 PM, Christophe Combelles wrote:
> Le 14/11/2011 01:52, Christophe Combelles a écrit :
>> Le 13/11/2011 14:22, Tres Seaver a écrit :
>>> If somebody who cares about the KGS could look at these failures
>>> and figure out why knew ve
This is the summary for test reports received on the
zope-tests list between 2011-11-13 00:00:00 UTC and 2011-11-14 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/
Le 14/11/2011 23:24, Tres Seaver a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/14/2011 04:50 PM, Christophe Combelles wrote:
>> Le 14/11/2011 01:52, Christophe Combelles a écrit :
>>> Le 13/11/2011 14:22, Tres Seaver a écrit :
>
If somebody who cares about the KGS could
Am 14.11.2011 um 23:24 schrieb Tres Seaver:
[...]
> I don't understand why r123334 was needed to "fix" the KGS buildout: I
> thought the KGS was "pinned" by virtue of using its 'versions.cfg' file:
>
> http://download.zope.org/zope3.4/3.4.1/versions.cfg
I think it would be a good idea to extend
On Tue, Nov 15, 2011 at 01:00:03AM +, Zope tests summarizer wrote:
> Non-OK results
> --
>
> [1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux
>https://mail.zope.org/pipermail/zope-tests/2011-November/052670.html
Looks like a network failure
> [2]FAILED winbot
