This is the summary for test reports received on the
zope-tests list between 2012-06-11 00:00:00 UTC and 2012-06-12 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/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/12/2012 05:05 AM, Patrick Gerken wrote:
>> [1]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
>> https://mail.zope.org/pipermail/zope-tests/2012-June/064225.html
>
> That one is new, but I start to believe that there is a harddrive or
> virus
On Tue, Jun 12, 2012 at 2:50 PM, Jan-Carel Brand wrote:
> Do you also sync the git repo with new changes from the svn repo?
Yes, but unfortunately
1. It takes ages
2. I have to do it on my laptop because none of my servers has enough
inodes for that task.
I do it once a day at the moment.
__
Hi Patrick
On Mon, 2012-06-11 at 18:36 +0200, Patrick Gerken wrote:
> Since I most often look for the history of something in SVN, I decided
> to finally make a git mirror for myself to quickly find the history of
> anything I might ever want.
> Since its for history only, I just imported the c
> [1] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
> https://mail.zope.org/pipermail/zope-tests/2012-June/064225.html
That one is new, but I start to believe that there is a harddrive or
virus or anything.
The error is a compilation error of c code in zope.security._proxy.c
The last chang
