P. Nagaraj wrote at 2006-8-16 17:29 +0530:

>Hi Diether,

Wow, the medieval spelling of my name :-)

> ...
>Your suggestion worked. But one error came up.
>[ZODB3-3.4.0]# python test.py
>Running tests from build/lib.linux-i686-2.3
>Running unit tests:
>Error in test testUmask (zdaemon.tests.testzdrun.ZDaemonTests)
>Traceback (most recent call last):
>   File "build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", line 75, in 
>     self.assertEqual(self.expect, output)
>   File "/var/tmp/python2.3-2.3.5-root/usr/lib/python2.3/unittest.py", line 
>302, in failUnlessEqual
>     raise self.failureException, \
>AssertionError: '' != '\n\nFailure in test testUmask 
>(zdaemon.tests.testzdrun.ZDaemonTests)\nTraceback (most recent call 
>last):\n  File "build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py", line 
>260, in testUmask\n    self.assert_(not os.access(path, os.W_OK))\n  File 
>"/var/tmp/python2.3-2.3.5-root/usr/lib/python2.3/unittest.py", line 278, 
>in failUnless\n    if not expr: raise self.failureException, 

I think you can ignore this failure in the "testUmask" test
of "zdaemon". Almost surely, you will not need this feature.

For me, the above looks like a broken test (at least I have
problems to decode the 'AssertionError').

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

Reply via email to