From: Nathaniel Talbott Date: 2003-12-05T22:56:14+09:00 Subject: Re: Problems with TestUnit On Dec 5, 2003, at 01:27, Dmitry V. Sabanin wrote: >> Actually, I was looking for the version (including date) of Ruby >> you're >> using. > Oh, sorry, I didn't understand that :) > My version is: > ruby 1.8.1 (2003-11-10) [i686-linux] That version would definitely be affected by the bug. Any version dated December or later should not be. >> This should be fixed in the latest CVS. If for some reason you can't >> use that, -d is the suggested work-around. > Strange, I just upgraded my cvs version, and I have the same problem > without -d. > I guess I need to investigate some more, maybe ruby looks for TestUnit > files in wrong load > path.. Well I've just checked, and it definitely seems to be working correctly in the most recent CVS: ntalbott@jacob:~/cvs/ruby$ ruby -v t.rb ruby 1.8.1 (2003-12-05) [powerpc-darwin] t.rb:3: unhandled exception ntalbott@jacob:~/cvs/ruby$ cat t.rb require 'test/unit' raise ntalbott@jacob:~/cvs/ruby$ So yes, you might be requiring an old set of Test::Unit files. Let me know if you can't get it working. HTH, Nathaniel <:((><