minitest-reporters: v1.3.1 raises loading errors
v1.3.1 started breaking all our builds this morning. I haven’t had a chance to investigate exactly why yet, but below is a stack trace.
Workaround: Rollback to v1.3.0
/Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:114:in `const_get': wrong constant name initialize (NameError)
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:114:in `block in load_constant'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `each'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `inject'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `load_constant'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:62:in `test_class'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:18:in `before_test'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/default_reporter.rb:37:in `before_test'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `block in run_with_hooks'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `each'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `run_with_hooks'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:960:in `run_one_method'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:334:in `run_one_method'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:321:in `block (2 levels) in run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:320:in `each'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:320:in `block in run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:360:in `on_signal'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:347:in `with_info_handler'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:319:in `run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `block in __run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `map'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `__run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:136:in `run'
from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:63:in `block in autorun'
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 11
- Comments: 20
this has broken my builds as well.
base_reporter tries to load the constant referenced by the test class name, but the name is not a valid constant name for classes defined by describe blocks. should not be trying to load the constant by this class name.
You don’t close an issue because there’s an open pull request. Instead, you reference the issue in the pull request so the issue auto-closes when the pull request is merged. ¯_(ツ)_/¯
the test is not failing 😦 Help needed.
My bad, mostly android developer nowdays and my current environment is not very friendly 😦 Windows)
I’m sorry, I should have done the PR myself. I’m wondering if you need to move one
end, so that the test is within the SpecReporterTest class. I’ll be back at work in 12 hours and can help more.