Run with code coverage fails in 2019.3 with chruby

Answered

I've been patiently waiting for this bug https://youtrack.jetbrains.com/issue/RUBY-23732 to be solved and once it got fixed I upgraded to 2019.3. Unfortunately running tests with code coverage doesn't seem to work anymore in my environment:

Testing started at 9:56 a.m. ...
/bin/bash -c ". /usr/local/Cellar/chruby/0.3.9/share/chruby/chruby.sh && chruby ruby-2.6.5 -rsimplecov_starter && /Users/myuser/work/projects/zetatango/bin/bundle exec /Users/myuser/.rubies/ruby-2.6.5/bin/ruby -Itest /Users/myuser/project/test/controllers/my_controller_test.rb"
/Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- simplecov (LoadError)
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Applications/RubyMine.app/Contents/plugins/ruby/rb/simplecov_starter.rb:11:in `<top (required)>'
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- simplecov (LoadError)
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Applications/RubyMine.app/Contents/plugins/ruby/rb/simplecov_starter.rb:11:in `<top (required)>'
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /Users/myuser/.rubies/ruby-2.6.5/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'

Process finished with exit code 1

I do have simplecov installed for this ruby version:

$ ls ~/.gem/ruby/2.6.5/gems/simplecov-0.17.1/
CHANGELOG.md CONTRIBUTING.md ISSUE_TEMPLATE.md LICENSE README.md doc lib

Any suggestions on how can I fix this?

Thanks,

Dragos

2 comments
Comment actions Permalink

Hello Dragos,

that issue hasn't been fixed in 2019.3, the fix version is set to 2020.1.

0
Comment actions Permalink

Ok, the bug did not have a fix version. I will be patient a little bit more. 

I will keep an eye on the EAP release

 

Thank you,

Dragos

0

Please sign in to leave a comment.