-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing minitest 5.0.8 breaks stdlib test/unit #358
Comments
Yes. That will happen. |
That's the point - I do NOT use them together. Minitest 5 is only installed. That alone is sufficient to break test/unit. (I do not even use minitest at all - that it is installed is because something else I installed comes with minitest 5 as a dependency) |
Yes, that alone is enough to break test/unit. You're using them together. test/unit uses minitest. If the gem is installed, it uses the latest version. I suggest you don't have minitest 5 installed globally if you use test/unit (tho, I can also suggest: don't use test/unit, use minitest and this problem goes away quickly). You can use bundler and similar solutions to install minitest into private repos instead. If you installed something w/o specifying |
FYI for anyone else with the same problem: I started seeing the same exception tonight with a gem that does legitimately specify minitest as a runtime dependency—Rubinius's test/unit gem. (Rubinius 2 distributes the stdlib as gems, e.g. @zenspider thanks for explaining, very helpful. |
This is an issue with test/unit (and possibly other gems with bad dependencies), not minitest. Closing. |
Try
If I do that, I get the following exception:
The text was updated successfully, but these errors were encountered: