1

A minitest is launched and ends up running, but in the meantime is now generating a series of warnings. Mise was very recently installed to replace rbenv. The warnings are:
.local/share/mise/installs/ruby/3.3.0/lib/ruby/site_ruby/3.3.0/rubygems/platform.rb:268: warning: previous definition of X64_LINUX_MUSL was here
for
JAVA, MSWIN, MSWIN64, MINGW, X64_MINGW, UNIVERSAL_MINGW, WINDOWS, X64_LINUX

These do not manifest when running in development.
The natural suspicion is that this behaviour is related to the MISE installation.

Re-running the same test, successively, does not generate the warning anymore.

How can this situation be resolved, if necessary?

5
  • 1
    Please add a minimal reproducible example. Commented Oct 31 at 6:45
  • The comment about reproducible is not practical; it would require posting a huge cross section of the application code, plus tons of fixtures. Commented Oct 31 at 6:56
  • 1
    A MRE is not about posting all the code that causes it, it is about posting the least amount of code possible to cause the issue. For instance if you just create and run a single test file does this happen? Also can you post a full stack trace for the warning as well as the command you are calling that is generating it? Commented Oct 31 at 18:48
  • 1
    it's just a warning, you can ignore it for the most part, but something is double loading. Commented Nov 3 at 11:26
  • Sounds like rbenv is still loading in your environment and then mise is loading Ruby again after rbenv has already loaded it. If you run echo $PATH do you see both an rbenv and a mise path? Commented Nov 19 at 5:47

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.