thekompanee / fuubar

The instafailing RSpec progress bar formatter
http://jeffkreeftmeijer.com/2010/fuubar-the-instafailing-rspec-progress-bar-formatter/
MIT License
955 stars 65 forks source link

Whenever running rake spec #73

Closed Streek closed 10 years ago

Streek commented 10 years ago

rake aborted! NameError: uninitialized constant RSpec::Core::Version /Users/streek/.rvm/gems/ruby-2.0.0-p481/gems/rspec-instafail-0.2.5/lib/rspec/instafail.rb:7:in <module:RSpec>' /Users/streek/.rvm/gems/ruby-2.0.0-p481/gems/rspec-instafail-0.2.5/lib/rspec/instafail.rb:1:in<top (required)>' /Users/streek/.rvm/gems/ruby-2.0.0-p481/gems/fuubar-1.2.1/lib/fuubar.rb:3:in <top (required)>' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:76:inrequire' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:76:in block (2 levels) in require' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:72:ineach' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:72:in block in require' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:61:ineach' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler/runtime.rb:61:in require' /Users/streek/.rvm/gems/ruby-2.0.0-p481@global/gems/bundler-1.6.2/lib/bundler.rb:132:inrequire'

jfelchner commented 10 years ago

@Streek I'm fairly certain that this is a setup issue and not a problem with fuubar itself. Additionally the 1.x branch is in maintenance mode. I welcome any pull requests with a test, but I'm probably not going to get to this myself.

For what it's worth, the 2.x branch (although it requires RSpec 3.x) has completely dropped the dependency for rspec-instafail.

Streek commented 10 years ago

Thanks. If I'm feeling fancy I might take a crack at it.

github-actions[bot] commented 3 years ago

This issue has been closed automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.