On Tue, 03 Feb 2004 00:09:16 +0900, Nathaniel Talbott wrote:

> On Feb 2, 2004, at 08:04, Simon Strandgaard wrote:
> 
>> A typical call stack of mine look like the following.
>> The last 10 lines is visual noise.  Is it possible to get
>> rid of these lines?
> 
> Test::Unit _is_ stripping the stack that it has control over:
> 
>>   1) Failure:
>> test_repeat_nested14(TestMScanner)
>>     [./common.rb:64:in `assert_regex'
>>      ./match_mixins.rb:548:in `_debug_test_repeat_nested14'
>>      (eval):5:in `test_repeat_nested14']:
> 
> Note that there is only a three line stack here. 

Ok. I just never have noticed these lines until now.  Earlier I have
looked at the _really_ long stack dump.


> The noise below is 
> somehow being caused by your use of Test::Unit. Why is...
> 
>> <["abababab", "ab"]> expected but was
> 
> ..an array being compared to...
> 
>> <#<RuntimeError: integrity: expected "a . b", got "a b a b a b a b" at 
>> line 4> /home/
> 
> .. a RuntimeError? Without seeing at least the structure of your code, 
> I can't figure out what's going on, but I don't think it's a Test::Unit 
> issue. I can only make it so smart :-)

Don't understand.


The way I use test::unit is..

require 'test/unit'
class TestMScanner < Test::Unit::TestCase 
	def test_me
	end
end
if $0 == __FILE__
	require 'test/unit/ui/console/testrunner'
	Test::Unit::UI::Console::TestRunner.run(TestMScanner, 3)
end 

When I execute it, it results in the _long_ stack dump.
Is it wrong?  :-)

--
Simon Strandgaard