[Zope-dev] Weird test failures with DateTime

2005-11-26 Thread Philipp von Weitershausen
Hi,

I've recently been seeing weird DateTime test failures on all Zope 2
branches since 2.7 (see below). Any idea what I'm doing wrong? My system
is OSX 10.3 with a self-compiled Python 2.4.1 (through darwinports). My
system timezone, as you can see, is GMT+0800 (Beijing time).


[EMAIL PROTECTED]:~/dev/Zope$ python test.py -s DateTime
Running tests at level 1
Running unit tests:
  Running:
.

Failure in test testAddPrecision (DateTime.tests.testDateTime.DateTimeTests)
Traceback (most recent call last):
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 260, in run
testMethod()
  File
/Users/philipp/dev/Zope/lib/python/DateTime/tests/testDateTime.py,
line 61, in testAddPrecision
dt)
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: 2005/11/26 19:22:40.649 US/Central

..

Failure in test testConstructor5 (DateTime.tests.testDateTime.DateTimeTests)
Traceback (most recent call last):
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 260, in run
testMethod()
  File
/Users/philipp/dev/Zope/lib/python/DateTime/tests/testDateTime.py,
line 89, in testConstructor5
self.assertEqual(str(dt), str(dt1), (dt, dt1))
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: (DateTime('2005/11/26 19:22:40.687 US/Central'),
DateTime('2005/11/26 05:22:40.687 US/Central'))

...

Failure in test testRFC822 (DateTime.tests.testDateTime.DateTimeTests)
Traceback (most recent call last):
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 260, in run
testMethod()
  File
/Users/philipp/dev/Zope/lib/python/DateTime/tests/testDateTime.py,
line 328, in testRFC822
self.assertEqual(dts[5], %+03d%02d % divmod( (-offset/60), 60) )
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: '-0600' != '+0800'



Failure in test testSubtraction (DateTime.tests.testDateTime.DateTimeTests)
Traceback (most recent call last):
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 260, in run
testMethod()
  File
/Users/philipp/dev/Zope/lib/python/DateTime/tests/testDateTime.py,
line 138, in testSubtraction
self.assertEqual(dt1, dt3, (dt, dt1, dt2, dt3))
  File
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/unittest.py,
line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: (DateTime('2005/11/26 19:23:18.686 US/Central'),
DateTime('2005/11/23 01:59:25.081 US/Central'), DateTime('2005/11/26
19:23:18.686 US/Central'), DateTime('2005/11/23 15:59:25.081 US/Central'))

..
  Ran 32 tests with 4 failures and 0 errors in 38.183 seconds.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Weird test failures with DateTime

2005-11-26 Thread Jens Vagelpohl


On 26 Nov 2005, at 11:43, Philipp von Weitershausen wrote:


Hi,

I've recently been seeing weird DateTime test failures on all Zope 2
branches since 2.7 (see below). Any idea what I'm doing wrong? My  
system
is OSX 10.3 with a self-compiled Python 2.4.1 (through  
darwinports). My

system timezone, as you can see, is GMT+0800 (Beijing time).


Running the tests under current 2.7/2.8 branches with Python 2.3.5 on  
OS X 10.4.3 things run fine:


--
tiny:/usr/local/zope/28Instance jens$ bin/zopectl test --libdir /usr/ 
local/zope/opt/Zope-2.8-branch/lib/python DateTime
Running tests via: /usr/local/bin/python /usr/local/zope/opt/Zope-2.8- 
branch/bin/test.py -v --config-file /usr/local/zope/28Instance/etc/ 
zope.conf --libdir /usr/local/zope/opt/Zope-2.8-branch/lib/python  
DateTime

Running unit tests at level 1
Running unit tests from /usr/local/zope/opt/Zope-2.8-branch/lib/python
Parsing /usr/local/zope/28Instance/etc/zope.conf

--
Ran 32 tests in 23.396s

OK
---

However, I am noticing that on the current Zope 2.9 branch, trying to  
build the software fails completely. The configure script works  
fine, but the make step does not seem to do anything at all. There  
is no error output, and all that's in the directory set as the -- 
prefix is the makefile:



 tiny:/usr/local/zope/opt/Zope-2.9-branch jens$ make
/usr/local/bin/python2.4 /usr/local/zope/src/Zope-2.9-branch/ 
setup.py \

build_ext -i
running build_ext

Zope built. Next, do 'make install' (or 'make instance'
to run a Zope instance directly from the build directory).

tiny:/usr/local/zope/opt/Zope-2.9-branch jens$ ls
makefile
-

INSTALL.txt still shows the configure/make/make install  
instructions and I was under the impression this was still supposed  
to work. How does everyone else build 2.9?


jens

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )