Refresh CI setup: test against newer Rubies, use official actions #41
EnvekAnnotations
5 errors
|
Puma 4 on Ruby 2.7
The current runner (debian-11-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 2.7.8 /__t/Ruby/2.7.8/x64
Once that completes successfully, mark it as complete with:
$ touch /__t/Ruby/2.7.8/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
Puma 5 on Ruby 3.0
The current runner (debian-11-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.0.7 /__t/Ruby/3.0.7/x64
Once that completes successfully, mark it as complete with:
$ touch /__t/Ruby/3.0.7/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
Puma 6 on Ruby 3.2
The current runner (debian-12-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.2.4 /__t/Ruby/3.2.4/x64
Once that completes successfully, mark it as complete with:
$ touch /__t/Ruby/3.2.4/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
Puma 6 on Ruby 3.3
The current runner (debian-12-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.1 /__t/Ruby/3.3.1/x64
Once that completes successfully, mark it as complete with:
$ touch /__t/Ruby/3.3.1/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
Puma 6 on Ruby 3.1
The current runner (debian-12-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.1.5 /__t/Ruby/3.1.5/x64
Once that completes successfully, mark it as complete with:
$ touch /__t/Ruby/3.1.5/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|