Docker-Compose in RubyMine 2017.3 Fails on Test::Unit Run Configurations with TeamCity error

I've set up a remote SDK and Test::Unit Run configuration in RubyMine but all I get is the following error in RubyMine's console:

Testing started at 6:05 AM ...
/usr/local/bin/ruby -e $$stdout.sync=true;$$stderr.sync=true;load($$0=ARGV.shift) -Itest /opt/.rubymine_helpers/rb/testing/runner/tunit_or_minitest_in_folder_runner.rb
/usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- teamcity/utils/runner_utils (LoadError)
from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /opt/.rubymine_helpers/rb/testing/runner/tunit_or_minitest_in_folder_runner.rb:25:in `<top (required)>'
from -e:1:in `load'
from -e:1:in `<main>'

Process finished with exit code 1

 

I use docker-compose installed by Docker for Mac and have no issues in Terminal running the following:

docker-compose run --rm web bundle install   
docker-compose build
docker-compose run --rm web bundle exec rake test

 

I've scoured the JetBrains docs on this and can't seem to find any hints as to what might be failing.  Any help would be much appreciated.

3 comments
Comment actions Permalink

Still having problems after setting everything up all over again in a brand new project, but for some reason the error has changed: 

Testing started at 11:13 AM ...
/usr/local/bin/ruby -e $$stdout.sync=true;$$stderr.sync=true;load($$0=ARGV.shift) -Itest /usr/app/test/functional/application_controller_test.rb --name=test_read_User-Agent_for_feature_gate_system
-e:1:in `require': cannot load such file -- test/unit/ui/teamcity/loadpath_patch.rb (LoadError)
0
Comment actions Permalink

Also of note, I don't seem to have any issues running tests in projects that use RSPEC.  This is something specific to Test::Unit.  I'm not using TeamCity for anything, and it seems like RubyMine insists on TeamCity for Test:Unit UI

0
Comment actions Permalink

Hello,

Deeply sorry for inconvenience, fix will be included into nearest bug-fix update RM-2017.3.1 EAP, please see: https://youtrack.jetbrains.com/issue/RUBY-20549.

0

Please sign in to leave a comment.