[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz] Bug in test framework
From: |
Tuukka Hastrup |
Subject: |
[Gzz] Bug in test framework |
Date: |
Wed, 23 Apr 2003 10:25:05 +0300 (EEST) |
I don't know how to fix a bug we saw today in the test framework -
running tests stopped at this:
Java stack traces:
---------------------------------------------------------------------------
org.nongnu.storm.impl.DirPool.testBlockTmpFile (Test that creating a
blocktmpfile out of a block)
Traceback (innermost last):
File "test.py", line 195, in ?
File "test.py", line 154, in main
File "test.py", line 175, in run
AttributeError: printStackTrace
make: *** [test] Error 255
When I commented out the printStackTrace call, the tests went through and
I got a more helpful Python stack trace:
org.nongnu.storm.impl.DirPool.testBlockTmpFile (Test that creating a
blocktmpfile out of a block)
Traceback (most recent call last):
File "org/nongnu/storm/StormPool.meta", line 101, in testBlockTmpFile
f = org.nongnu.storm.BlockTmpFile.get(block)
AttributeError: module 'org.nongnu.storm' has no attribute 'BlockTmpFile'
I fixed that, but don't understand how the test system should have handled
this. Should it maybe handle Java exceptions and Python exceptions as
either and not as both?
--
-- Trying to catch me? Just follow up my Electric Fingerprints
-- To help you: address@hidden
http://www.iki.fi/Tuukka.Hastrup/
IRCNet: Stugge/tuukkah @#pii,#fenfire,#ynna
Jabber ID: address@hidden, ICQ #11321669
- [Gzz] Bug in test framework,
Tuukka Hastrup <=