On Fri, Oct 30, 2009 at 9:05 AM, Stefano Crocco <stefano.crocco / alice.it> w=
rote:
> On Thursday 29 October 2009, Michael Guterl wrote:
>> |On Mon, Oct 26, 2009 at 7:37 PM, Tony Arcieri <tony / medioh.com> wrote:
>> |> I don't know exactly when this started happening, but it seems like
>> |> RSpec recently started swallowing huge chunks of the backtrace.
>> |> =C2=A0Sometimes I don't even get one.
>> |>
>> |> This is making it extremely annoying to debug as I'm unable to see wh=
ere
>> |> the error is occurring.
>> |>
>> |> Anyone know what's up?
>> |
>> |I started noticing the same thing today:
>> |
>> |1)
>> |NoMethodError in 'XML::Importer should extract a list of jobs from the
>> |provided XML'
>> |You have a nil object when you didn't expect it!
>> |The error occurred while evaluating nil.text
>> |
>> |Finished in 0.03372 seconds
>> |
>> |1 example, 1 failure
>> |
>> |It would be awesome to know what line that was occurring on...
>> |
>> |Best,
>> |Michael Guterl
>> |
>
> I noticed something like that recently (at least using ruby 1.9) and solv=
ed it
> by passing the -b option to spec. I don't know the reason for this change=
. I
> tried looking at the rspec CHANGELOG but it didn't show anything related =
(at
> least, I didn't recognize it).
>
> I hope this helps
>
Thanks, this helps, now when I need a detailed backtrace I can just
add -b to spec/spec.opts

Michael Guterl