[Zope3-dev] Zope3 Tests not OK :-(

Tim Peters tim_one@email.msn.com
Fri, 29 Nov 2002 01:11:18 -0500


[Tim]
> Try zeroing in on just one of the ZEO tests failing for you; the
> same root cause probably underlies all of them.  Run it in isolation
> with -300 logging -- maybe something useful will show up in the log
> file.

[Godefroid Chapelle]
> Could you tell me what you mean and how I am supposed to do that ?

Here's a wholly concrete example:

C:\Code\Zope3>set STUPID_LOG_FILE=/code/stupid.txt
C:\Code\Zope3>set STUPID_LOG_SEVERITY=-300
C:\Code\Zope3>\python22\python test.py -vv . checkDisconnectionError
checkDisconnectionError (ZEO.tests.testConnection.WindowsConnectionTests)
... ok


----------------------------------------------------------------------
Ran 1 tests in 3.180s

OK

C:\Code\Zope3>C:\Code\Zope3>dir ..\stup*

 Volume in drive C has no label
 Volume Serial Number is 3459-5C23
 Directory of C:\Code

STUPID   TXT         3,226  11-29-02  1:04a stupid.txt
         1 file(s)          3,226 bytes
         0 dir(s)          502.17 MB free

C:\Code\Zope3>notepad ..\stupid.txt

Presumably the checkDisconnectionError step fails for you.  Try Python 2.2.2
first, though.  We released 2.2.2 mostly to fix 2.2.1 bugs that affected
Zope.