[Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Sat May 29 12:00:00 2010 UTC to Sun May 30 12:00:00 2010 UTC. There were 19 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in

Re: [Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Adam GROSZER
ZTS Test failures ZTS - ZTS Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux ZTS From: ccomb at free.fr ZTS Date: Sun May 30 00:29:38 EDT 2010 ZTS URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014714.html Huhh? Last change was 4 days ago. Let's see what happens

Re: [Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: ZTS Test failures ZTS - ZTS Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux ZTS From: ccomb at free.fr ZTS Date: Sun May 30 00:29:38 EDT 2010 ZTS URL:

Re: [Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Christophe Combelles
Le 30/05/2010 15:33, Tres Seaver a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam GROSZER wrote: ZTS Test failures ZTS - ZTS Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux ZTS From: ccomb at free.fr ZTS Date: Sun May 30 00:29:38 EDT 2010 ZTS

Re: [Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Sebastien Douche
On Sun, May 30, 2010 at 17:44, Christophe Combelles cc...@free.fr wrote: There is something wrong with zdaemon tests: Now I have no builder running, but: $ ps -ef | grep zdaemon | wc -l 74 Another big problem is /tmp filling with crap: $ ls -1 /tmp/ | grep tmp | wc -l 3726 Hi Christophe,

[Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-25 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Mon May 24 12:00:00 2010 UTC to Tue May 25 12:00:00 2010 UTC. There were 19 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in