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

Closed
carols10cents opened this Issue Oct 3, 2012 · 7 comments

Comments

Projects
None yet
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

This comment has been minimized.

Show comment
Hide comment
@qrush

qrush Oct 3, 2012

Owner

Yikes :( I wonder if something changed lately with mini test's API.

Basically, this is returning nil: https://github.com/qrush/m/blob/master/lib/m.rb#L191

Maybe we should just .to_i it? Does that work if you edit it locally?

On Wednesday, October 3, 2012 at 10:17 AM, Carol Nichols wrote:

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:inexecute' 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:inrun' 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:inload' from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/bin/m:23:in `

'
I was poking around some other issues and noticed this error is the 2nd in the screenshot in this comment: qrush/m#16 (#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....


Reply to this email directly or view it on GitHub (#20).

Owner

qrush commented Oct 3, 2012

Yikes :( I wonder if something changed lately with mini test's API.

Basically, this is returning nil: https://github.com/qrush/m/blob/master/lib/m.rb#L191

Maybe we should just .to_i it? Does that work if you edit it locally?

On Wednesday, October 3, 2012 at 10:17 AM, Carol Nichols wrote:

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:inexecute' 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:inrun' 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:inload' from /Users/carolnichols/.rvm/gems/ruby-1.9.3-p194@apangea/bin/m:23:in `

'
I was poking around some other issues and noticed this error is the 2nd in the screenshot in this comment: qrush/m#16 (#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....


Reply to this email directly or view it on GitHub (#20).

@carols10cents

This comment has been minimized.

Show comment
Hide comment
@carols10cents

carols10cents Oct 11, 2012

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 :(

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

This comment has been minimized.

Show comment
Hide comment
@brandonweiss

brandonweiss Nov 5, 2012

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.

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 comment has been minimized.

Show comment
Hide comment
@coreypurcell

coreypurcell Dec 2, 2012

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

See this issue there. TwP/turn#111

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

See this issue there. TwP/turn#111

@carols10cents

This comment has been minimized.

Show comment
Hide comment
@carols10cents

carols10cents Dec 3, 2012

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!

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

This comment has been minimized.

Show comment
Hide comment
@bcardarella

bcardarella Jan 18, 2013

Contributor

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

Contributor

bcardarella commented Jan 18, 2013

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

@coreypurcell

This comment has been minimized.

Show comment
Hide comment
@coreypurcell

coreypurcell Jan 18, 2013

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

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