My application was running fine, but recently it started giving MemoryError:
--
2009-07-24T05:31:57 ERROR ZODB.Connection Couldn't load state for 0x1d30bb
Traceback (most recent call last):
File
/opt/front1/builds/F2.16/opt/Zope-2.8.8-final/lib/python/ZODB/Connection.py,
line 704, in
On 24.07.09 09:33, Rupesh P Raj wrote:
My application was running fine, but recently it started giving
MemoryError:
Problem persists after a restart?
-aj
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
yes
On Fri, Jul 24, 2009 at 1:06 PM, Andreas Jung li...@zopyx.com wrote:
On 24.07.09 09:33, Rupesh P Raj wrote:
My application was running fine, but recently it started giving
MemoryError:
Problem persists after a restart?
-aj
___
Zope-Dev
On 24.07.09 09:37, Rupesh P Raj wrote:
yes
On Fri, Jul 24, 2009 at 1:06 PM, Andreas Jung li...@zopyx.com
mailto:li...@zopyx.com wrote:
On 24.07.09 09:33, Rupesh P Raj wrote:
My application was running fine, but recently it started giving
MemoryError:
Problem persists
Summary of messages to the zope-tests list.
Period Thu Jul 23 12:00:00 2009 UTC to Fri Jul 24 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Thu Jul 23 20:50:04 EDT
On Fri, Jul 24, 2009 at 2:38 AM, Wolfgang Schnerringw...@wosc.de wrote:
Log message for revision 102202:
when a test module does not define a test_suite, first try to load
any unittest.TestCase descendants in it before complaining it does not
contain any tests
I'd rather zope.testing support
* Benji York be...@zope.com [2009-07-24 08:02]:
On Fri, Jul 24, 2009 at 2:38 AM, Wolfgang Schnerringw...@wosc.de wrote:
Log message for revision 102202:
when a test module does not define a test_suite, first try to load
any unittest.TestCase descendants in it before complaining it does not
Andreas Jung wrote:
On 23.07.09 12:10, yuppie wrote:
Any thoughts? Is the 2.12 branch still open for changes like that?
Go ahead. I also had to fix a similar issue some days ago inside
Zope startup code.
Done.
http://svn.zope.org/?rev=102230view=rev
http://svn.zope.org/?rev=102231view=rev
