On Wed, Dec 19, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
[4]FAILED winbot / zope.exceptions_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-December/070321.html
This may be related to my recent fixes and some fallout from using \r\n
line endings. I'll try to
On Wed, Dec 19, 2012 at 11:56:07AM +0200, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
[4]FAILED winbot / zope.exceptions_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-December/070321.html
This may be related to my
On Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche sdou...@gmail.com wrote:
I worked a bit this weekend on the buildbot for Python 3.3:
Another small step:
Develop:
'/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.security'
include/zope.proxy/proxy.h:36:17: warning:
On Wed, Dec 19, 2012 at 04:28:16PM +0200, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 11:56:07AM +0200, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
[4]FAILED winbot / zope.exceptions_py_265_32
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 09:53 AM, Sebastien Douche wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche sdou...@gmail.com
wrote:
I worked a bit this weekend on the buildbot for Python 3.3:
Another small step: Develop:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 11:28 AM, Tres Seaver wrote:
On 12/19/2012 09:53 AM, Sebastien Douche wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche
sdou...@gmail.com wrote:
I worked a bit this weekend on the buildbot for Python 3.3:
Another small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 11:33 AM, Tres Seaver wrote:
I spoke in error: the zope.proxy extension is ported. However, there
is a chunk of 'proxy.h' which is *not* compiled when building the
extension itself: it is only compiled when included in another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/18/2012 08:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / BTrees_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-December/070320.html
This one is on me: the tests for out-of-bounds keys / wraparound are
failing on
On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote:
On 12/19/2012 11:33 AM, Tres Seaver wrote:
I spoke in error: the zope.proxy extension is ported. However, there
is a chunk of 'proxy.h' which is *not* compiled when building the
extension itself: it is only compiled when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 01:34 PM, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote:
On 12/19/2012 11:33 AM, Tres Seaver wrote:
I spoke in error: the zope.proxy extension is ported. However,
there is a chunk of 'proxy.h'
On Wed, Dec 19, 2012 at 01:22:00PM -0500, Tres Seaver wrote:
On 12/18/2012 08:00 PM, Zope tests summarizer wrote:
[2]FAILED winbot / z3c.ptcompat_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-December/070297.html
No idea what cased this failure: the package hasn't
On Wed, Dec 19, 2012 at 01:37:04PM -0500, Tres Seaver wrote:
On 12/19/2012 01:34 PM, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote:
On 12/19/2012 11:33 AM, Tres Seaver wrote:
I spoke in error: the zope.proxy extension is ported. However,
there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 01:57 PM, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:37:04PM -0500, Tres Seaver wrote:
On 12/19/2012 01:34 PM, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote:
On 12/19/2012 11:33 AM, Tres
This is the summary for test reports received on the
zope-tests list between 2012-12-18 00:00:00 UTC and 2012-12-19 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:
14 matches
Mail list logo
