[Zope-dev] Linux x86_64 [Was: Zope Tests: 3 OK, 5 Failed]

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan H. Holek wrote:
> All failures appear to be due to the new box running Linux x86_64.  
> Tests still pass fine on the Mac.
> 
> Any experience with this? MemoryError in Acquisition? WTH?

I can reproduce the OFS.tests.testRange failures on my x86_64 box:

 $ uname -a
 Linux mred 2.6.27-14-generic #1 SMP Wed Apr 15 19:29:46 UTC \
   2009 x86_64 GNU/Linux
 $ cd /tmp
 $ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk
 $ cd Zope-trunk
 $ /opt/Python-2.6.2/bin/python bootstrap.py
 ...
 $ bin/buildout
 ...
 $ bin/test --all
 ...
 Failure in test testMultipleRangesBigFileOutOfOrder
    (OFS.tests.testRanges.TestRequestRange)
 Traceback (most recent call last):
   File "/opt/Python-2.6.2/lib/python2.6/unittest.py", line 279, in run
    testMethod()
   File "/home/tseaver/projects/Zope-trunk/src/OFS/tests/testRanges.py",
     line 332, in testMultipleRangesBigFileOutOfOrder
     (70000, 80001)])
   File "/home/tseaver/projects/Zope-trunk/src/OFS/tests/testRanges.py",
     line 209, in expectMultipleRanges
     str(len(body)), rsp.getHeader('content-length')))
   File "/opt/Python-2.6.2/lib/python2.6/unittest.py", line 321, in
     failIf
     if expr: raise self.failureException, msg
 AssertionError: Incorrect Content-Length is set! Expected 20425,
     got 20426.

I don't grok the range support code at all:  probably Martijn Pieters is
the only person in the world who does.  The tests are quite obscure to
me, so I can't diagnose even whether the failure is a testing artifact
or a real bug.

I see another failure in a test Hanno recently added:

 Failure in test test_datetime
(Products.PluginIndexes.DateRangeIndex.tests.test_DateRangeIndex.DRI_Tests)
 Traceback (most recent call last):
   File "/opt/Python-2.6.2/lib/python2.6/unittest.py", line 279, in run
    testMethod()
   File
"/home/tseaver/projects/Zope-trunk/src/Products/PluginIndexes/DateRangeIndex/tests/test_DateRangeIndex.py",
line 155, in test_datetime
     self.assertEqual(work.getEntryForObject(0), (20790915, 20790990))
   File "/opt/Python-2.6.2/lib/python2.6/unittest.py", line 350, in
failUnlessEqual
    (msg or '%r != %r' % (first, second))
AssertionError: (20791275, 20791350) != (20790915, 20790990)

This one looks to be the result of using "naive" datetime objects while
expecting them to be converted to hard-wired integers, so that tests
which pass on Hanno's machine fail on mine, because of different timezones.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKZe9j+gerLs4ltQ4RAl4nAKDJQyWHdnlEEQv1zbQJeJiR7gGuTACfQxDi
n5GO/tP+jpRhqUddn2CbaKg=
=RdUR
-----END PGP SIGNATURE-----