> I'd prefer a cleaner backtrace, but maybe we could warn that the filters where suppressing the backtrace? Suggesting to the user they should run rspec --backtrace to see the full backtrace?

I'd be OK with this if I thought that this is behavior any user would ever want...but I don't.  Can you think of a situation where a user would want no backtrace at all?  It would be especially frustrating if it was a very slow example.  As a user, I'd be annoyed that RSpec was making me run it again with that flag to get the info I'm after rather than just giving it to me the first time.

> including a message and the full backtrace satisfies that confusion for me. WDYT?

:+1: