Skip to content

Instantly share code, notes, and snippets.

@MSch
Created July 7, 2010 16:25
Show Gist options
  • Save MSch/466908 to your computer and use it in GitHub Desktop.
Save MSch/466908 to your computer and use it in GitHub Desktop.
msch@iMartin:~/projects/inviteapp (master)$ rspec --drb
Exception encountered: #<NoMethodError: undefined method `configure' for ["--color"]:Array>
backtrace:
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/rspec-core-2.0.0.beta.16/lib/rspec/core/command_line.rb:11:in `run'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/rspec-core-2.0.0.beta.16/lib/rspec/monkey/spork/test_framework/rspec.rb:4:in `run_tests'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:13:in `block in run'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/forker.rb:21:in `block in initialize'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/forker.rb:18:in `fork'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/forker.rb:18:in `initialize'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:9:in `new'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/run_strategy/forking.rb:9:in `run'
/Users/msch/.rvm/gems/ruby-1.9.2-rc1@rails3/gems/spork-0.8.4/lib/spork/server.rb:47:in `run'
/Users/msch/.rvm/rubies/ruby-1.9.2-rc1/lib/ruby/1.9.1/drb/drb.rb:1558:in `perform_without_block'
/Users/msch/.rvm/rubies/ruby-1.9.2-rc1/lib/ruby/1.9.1/drb/drb.rb:1518:in `perform'
/Users/msch/.rvm/rubies/ruby-1.9.2-rc1/lib/ruby/1.9.1/drb/drb.rb:1592:in `block (2 levels) in main_loop'
/Users/msch/.rvm/rubies/ruby-1.9.2-rc1/lib/ruby/1.9.1/drb/drb.rb:1588:in `loop'
/Users/msch/.rvm/rubies/ruby-1.9.2-rc1/lib/ruby/1.9.1/drb/drb.rb:1588:in `block in main_loop'
@saberma
Copy link

saberma commented Jul 9, 2010

try uninstall rspec and its extension (rspec-core, rspec-mocks etc), and reinstall 2.0.0.beta.15

@MSch
Copy link
Author

MSch commented Jul 9, 2010

I did the opposite: I upgraded to rspec-core master, the bug's fixed there too :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment