[TransWarp] Test suite fails

[Vineet Jain]

I'm on windows XP professional and I have windows 200 professional at
work. I just ran the individual test suites and the model test suite is
what crashes the interpreter.


C:\>python c:\win32app\python22\lib\unittest.py
peak.binding.tests.test_suite 
...................
----------------------------------------------------------------------
Ran 19 tests in 0.691s

OK


C:\>python c:\win32app\python22\lib\unittest.py
peak.config.tests.test_suite 
.....................
----------------------------------------------------------------------
Ran 21 tests in 0.561s

OK
C:\>python c:\win32app\python22\lib\unittest.py
peak.model.tests.test_suite 
<Crashed Interpreter>

C:\>python c:\win32app\python22\lib\unittest.py
peak.naming.tests.test_suite 
...
----------------------------------------------------------------------
Ran 3 tests in 0.921s

C:\>python c:\win32app\python22\lib\unittest.py
peak.util.tests.test_suite 
..............................
----------------------------------------------------------------------
Ran 30 tests in 0.421s

OK


C:\>python c:\win32app\python22\lib\unittest.py peak.tests.test_suite 
No output.

Vineet



-----Original Message-----
From: Phillip J. Eby [mailto:pje at telecommunity.com] 
Sent: Wednesday, May 14, 2003 10:47 AM
To: Vineet Jain; ueck at net-labs.de
Cc: transwarp at eby-sarna.com
Subject: RE: [TransWarp] Test suite fails

At 10:26 AM 5/14/03 -0700, Vineet Jain wrote:
>Thanks Ulrich.
>
>I tried the unit test cases and the example at work (on a different
>computer) with the python distribution from python.org and both of them
>crashed the interpreter.

That is utterly baffling to me.  Unfortunately, it sounds like there is 
something that's independent of which Python version you use.  Perhaps
it 
is something else, then, like the OS version.  I work exclusively on 
Windows 98 SE; what OS are you on?  Also, perhaps you could try running 
individual test suites, i.e.

peak.binding.tests.test_suite
peak.config.tests.test_suite
peak.model.tests.test_suite
peak.naming.tests.test_suite
peak.util.tests.test_suite

and see which ones crash.  It also seems bizarre to me that you're not 
getting any test output.  You should see a line of dots go by, followed
by 
a "126 tests run in blah blah seconds".

Also, if there's anybody else here with Windows who can confirm or deny 
whether the binary installer version of 0.5a1 works for them, and if so,
on 
what operating system, then that would be helpful.  Meanwhile, I'll try 
installing the binary version myself on a relatively fresh PC (also 98SE

I'm afraid) and see what happens.  But I won't be able to do that until 
tomorrow or so.



>I then downloaded the latest code from cvs and tried to rebuild it but
>don't have cl.exe (microsoft's c compiler) and it fails on building
>kjbuckets.

There are instructions in the Python manual that's called "Installing 
Python Modules" for how to use the free MinGW tools to build 
extensions.  But I expect that won't help you since the MinGW-built
modules 
are what I distributed with the binary.  Unless it's a OS or libraries 
versioning issue, in which case it might help.


>Is it not possible to have the default distribution contain only python
>code and if optimization is enabled then use the c code?

No.  The persistence code from ZODB is in C, so you couldn't use PEAK
for 
much then.