[Zope3-dev] RE: win32 Zope 3 Tests

[Tim Peters]

[Godefroid Chapelle]
> when running
>
> python test.py -vv "!ZEO\\tests\\testConnection"
>
> I get the following result
>
> ======================================================================
> FAIL: checkTimeStamp (ZODB.tests.testTimeStamp.TimeStampTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File
> "c:\tmp\Zope3TestsSandbox\Zope3\lib\python\ZODB\tests\testTimeStamp.py",
> line 127, in checkTimeStamp
>      self.assertEquals(cmp(t1, t), 1)
>    File "C:\Python22\lib\unittest.py", line 286, in failUnlessEqual
>      raise self.failureException, \
> AssertionError: 21 != 1
>
> ----------------------------------------------------------------------
> Ran 2698 tests in 1175.891s
>
> FAILED (failures=1)
>
> This implies that the fact that I am using Borland Compiler to build
> extensions seems to not be a problem.

I don't understand how that conclusion follows.  The "new" failure you see
here is unique to your platform, and appears due to that the Borland
memcmp() doesn't work like the MS memcmp().  The implementation of
TimeStamp_compare should be worming around this, though, so this one is a
bug in the Zope code.

> Further, this implies that the multiple "connection refused" I already
> mentioned in
> http://lists.zope.org/pipermail/zope3-dev/2002-November/003896.html seem
> also not to be related to the Borland Compiler built.

I don't thihk that follows.

> IOW, I have the feeling that it would really be worth to examine
> the problem.

Probably, but I don't know anything about the Borland environment, and am at
a loss how to help you.  Does Python's test suite all pass?  It contains
socket tests.