Skip to content
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

Support Ruby 3.0.3 releases #373

Closed
jrgriffiniii opened this issue Nov 29, 2021 · 5 comments · Fixed by #396
Closed

Support Ruby 3.0.3 releases #373

jrgriffiniii opened this issue Nov 29, 2021 · 5 comments · Fixed by #396

Comments

@jrgriffiniii
Copy link
Contributor

Derived from samvera/maintenance#77

@jrgriffiniii jrgriffiniii changed the title Support Ruby 3.0 releases Support Ruby 3.0.3 releases Mar 24, 2022
@jrgriffiniii
Copy link
Contributor Author

Rails 5.2.z and 5.1.z releases are failing with the following on Ruby 3.0.3:

image

(https://app.circleci.com/pipelines/github/samvera/browse-everything/201/workflows/20d16daa-34be-43b0-850f-66e45f32ee2f/jobs/1466)

Perhaps this is somehow related to the Ruby release which is being used? Please note that the Docker Image is referencing the following Ruby directory:

/home/circleci/project/vendor/bundle/ruby/3.0.0

@jrgriffiniii
Copy link
Contributor Author

samvera/samvera-circleci-orb#55 is blocking this.

@jrgriffiniii
Copy link
Contributor Author

There are now additional failures for the CircleCI build for 3.0.3 Ruby releases:

Using bootstrap 4.6.1
Errno::ENOENT: No such file or directory @ rb_sysopen -
/home/circleci/project/vendor/bundle/ruby/3.0.0/specifications/puma-3.12.6.gemspec
An error occurred while installing sync (0.5.0), and Bundler cannot
continue.
Make sure that `gem install sync -v '0.5.0' --source 'https://rubygems.org/'`
succeeds before bundling.

In Gemfile:
  coveralls was resolved to 0.7.1, which depends on
    term-ansicolor was resolved to 1.7.1, which depends on
      tins was resolved to 1.31.0, which depends on
        sync

Exited with code exit status 5
CircleCI received exit code 5

@jrgriffiniii
Copy link
Contributor Author

samvera/maintenance#81 (comment) was discovered when addressing this. I shall adjust accordingly.

@jrochkind
Copy link
Contributor

Rails 5.2 is not supported on ruby 3, so that test failure is expected. Just don't test 5.2 on Ruby 3+.

rails/rails#40938 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
2 participants