I'm getting a full backtrace (including rspec code) even though I'm not passing the --backtrace option.
You should be able to reproduce by cloning thor, adding a failing spec, and running the specs.
git clone git://github.com/wycats/thor.git
# Add a failing expectation
bundle exec thor spec
Apparently this is a dupe of #754. It looks like it's happening because I keep my development gems in ~/Projects/Ruby/gems. Is there any workaround that doesn't require renaming my directory tree?
Could you add a --no-backtrace flag that I could put in my global ~/.rspec file?
I was able to workaround the issue by renaming my directory and creating a symlink called gems. I'm not in love with that solution, but it works. 😥
It seems like you could whitelist the directory that the specs are being run from, no?
Sorry about the trouble. Did my fix in 356f15a for #754 cause this?
Anyhow, your suggestions to add --no-backtrace and whitelisting the current directory both sound reasonable. I'll try to get to this soon.
I meant to get to this right away, but have been busy with other issues. I think I've figured out the right solution here if someone wants to take a stab at this:
If anyone wants to take a stab at this, comment here so we know. If not, I'll try to get to it at some point.
@myronmarston I can probably build this out on sunday this week 😄.
@samphippen -- sounds great, thanks for taking a stab at it!
This got addressed by @samphippen in #843, which I've just merged.
@sferik -- want to give rspec master and shot and see if it works for your setup?
I can confirm that this issue is fixed in master. 🚢 it!