Skip to content

Loading…

No implicit conversion from nil to integer (TypeError) #20

Closed
carols10cents opened this Issue · 7 comments

5 participants

@carols10cents

Hi, I'm using m 1.2.1, ruby 1.9.3-p194, and running one test file with m crashes with this error:

m-1.2.1/lib/m.rb:191:in `exit': no implicit conversion from nil to integer (TypeError)
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/gems/m-1.2.1/lib/m.rb:191:in `execute'
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/gems/m-1.2.1/lib/m.rb:120:in `run'
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/gems/m-1.2.1/lib/m.rb:105:in `run'
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/gems/m-1.2.1/bin/m:4:in `<top (required)>'
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/bin/m:23:in `load'
from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/bin/m:23:in `<main>'

I was poking around some other issues and noticed this error is the 2nd in the screenshot in this comment: #16 (comment)

But that issue has been fixed, soooo... I don't know :-/

A few more potentially relevant gems, I can post the whole gemfile if it would be helpful:

  • minitest (3.2.0)
  • minitest-spec-rails (3.0.5)

I can try to narrow down the environment more if that would be useful....

@qrush
Owner
@carols10cents

Sorry for the delay in getting back to you on this-- changing that line to:

exit MiniTest::Unit.runner.run(test_arguments).to_i

makes it not crash, but now it's not finding any tests to run :(

@brandonweiss

I just tried m for the first time and am getting this error as well. I'm using ruby 1.9.3-p194 and minitest 4.1.0, and I'm using MiniTest::Spec.

@coreypurcell

This only occurs when the turn gem is installed. @carols10cents try it again without Turn installed.

See this issue there. turn-project/turn#111

@carols10cents

Wowwww I have no idea how you figured that out @coreypurcell but that's exactly it, thank you!! Removed turn and m works great. \m/

Also I didn't know that github does cross-project issue mentions, that's also pretty cool.

Closing this since it's a turn issue!

@bcardarella

Should this have been closed? Compatibility with turn seems important.

@coreypurcell

I'm pretty sure it's a turn issue, and it should be fixed there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.