[rspec-users] cleaner failure messages?

David Chelimsky dchelimsky at gmail.com
Tue Jun 22 12:08:37 EDT 2010

On Jun 22, 2010, at 10:27 AM, rogerdpack wrote:

>>>    Failure/Error: Unable to find matching line from backtrace
>>> Perhaps it isn't quite windows friendly?
>> That happens now and then when the error is in code generated with eval(string) with no file and ref numbers. Has nothing to do with Windows as far as I know, and is the same problem we have with ruby-debug.
> Interesting.
> I get the same thing with Linux.
> If I add the word "fail" to an rspec, it says the same (not an eval
> string...)...
> Here's the output if I run it -b
> 1) Gem speeding Gem.bin_path the fake sick way should fake guess the
> right path instead of loading full rubygems for now
>    Failure/Error: Unable to find matching line from backtrace
>    # spec.faster_rubygems.rb:29:in `block (3 levels) in <main>'
>    # /home/rdp/installs/ruby-1.9.1-p376_installed/lib/ruby/gems/1.9.1/
> gems/rspec-core-2.0.0.beta.12/lib/rspec/core/example.rb:47:in
> `instance_eval'

Please file an issue at http://github.com/rspec/rspec-core/issues

Feel free to reference the method that handles this:



More information about the rspec-users mailing list