Unable to use ruby 2.3.0 on OS X images

[segiddins]

See https://travis-ci.org/CocoaPods/CocoaPods/jobs/98784787 for the full log. Relevant bit is:

$ rvm use 2.3.0 --install --binary --fuzzy
ruby-2.3.0 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3.0 do rvm gemset create ' first, or append '--create'.

[BanzaiMan]

RVM is failing to install statically built binaries. I opened rvm/rvm#3591.

[abonas]

Same issue happens on Ubuntu images:
example can be seen here

$ rvm use 2.3 --install --binary --fuzzy
ruby-2.3 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3 --install --binary --fuzzy" failed and exited with 2 during .

System info:
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise
Linux Version 3.13.0-29-generic

[roidrage]

@abonas That's because our current rvm version doesn't yet know 2.3 as an alias for 2.3.0. You can get it to work by specifying 2.3.0 instead of 2.3.

[abonas]

@abonas That's because our current rvm version doesn't yet know 2.3 as an alias for 2.3.0. You can get it to work by specifying 2.3.0 instead of 2.3.

thanks for your reply. any eta for 2.3 to be recognized?

[roidrage]

Enabling 2.3 to be recognized requires a build environment update, and I don't have an ETA on that yet, sorry.

[thomasfedb]

@roidrage Any idea if this is something we'll see in days/weeks/months? We have an issue in @carrierwaveuploader that's blocking on this.

[segiddins]

FWIW, even specifying 2.3.0 causes a failure on OS X

[BanzaiMan]

@segiddins What error do you see right now?

[segiddins]

https://travis-ci.org/CocoaPods/CocoaPods/jobs/98784787

[segiddins]

@BanzaiMan any other info I can get you? I recently shipped a 2.3.0 bug because CI couldn't catch it

[jbender]

@segiddins while definitely not ideal, you can temporarily work around this by adding the following:

before_install:
  - rvm get stable --auto-dotfiles
  - rvm install 2.3.0

[segiddins]

@jbender how would I do that with my existing set of different ruby versions?

[jbender]

@segiddins haven't done it so take this with a grain of salt, but this might point you in the right direction:

matrix:
  include:
    - rvm: ruby-head
      before_install:
        - rvm get stable --auto-dotfiles
        - rvm install 2.3.0

You can explicitly add new things into your matrix (see https://docs.travis-ci.com/user/customizing-the-build/#Explicity-Including-Builds)

[pirj]

@jbender as per travis-yaml lint:

in matrix.include section: unexpected key before_install, dropping

[lolgear]

same

Version 2.2.5

[vishrutshah]

We just noticed this issue in travis-ci as it was working since while. Is this issue resurfaced recently, again?

https://travis-ci.org/Azure/autorest/builds/165382027

cc: @BanzaiMan

[BanzaiMan]

@vishrutshah That job is running on Trusty. I don't think that's related to this issue.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues