Skip to content
test

CI againt for Ruby 3.3 #249

Sign in to view logs

CI againt for Ruby 3.3

CI againt for Ruby 3.3 #249

Triggered via pull request December 28, 2023 05:41
@sue445sue445
synchronize #366
ruby3.3
Status Failure
Total duration 4m 7s
Artifacts –

test.yml

on: pull_request
Matrix: test_main
notify
0s
notify
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
test_main (2.3) / unit
Error: Unable to locate executable file: bundle. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. at Object.<anonymous> (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8224:27) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8077:58)
test_main (2.4) / unit
Error: Unable to locate executable file: bundle. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. at Object.<anonymous> (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8224:27) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8077:58)
test_main (2.7, --jit) / integration-docker (ubuntu:trusty)
The process '/opt/hostedtoolcache/Ruby/2.7.8/x64/bin/gem' failed with exit code 1
test_main (2.7, --jit) / integration-local
The process '/opt/hostedtoolcache/Ruby/2.7.8/x64/bin/gem' failed with exit code 1
test_main (2.5) / unit
Error: Unable to locate executable file: bundle. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. at Object.<anonymous> (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8224:27) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/ruby/setup-ruby/v1/dist/index.js:8077:58)
test_main (2.3) / unit
The following actions uses node12 which is deprecated and will be forced to run on node16: lazy-actions/slatify@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test_main (2.4) / unit
The following actions uses node12 which is deprecated and will be forced to run on node16: lazy-actions/slatify@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test_main (2.7, --jit) / integration-docker (ubuntu:trusty)
The following actions uses node12 which is deprecated and will be forced to run on node16: lazy-actions/slatify@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test_main (2.7, --jit) / integration-local
The following actions uses node12 which is deprecated and will be forced to run on node16: lazy-actions/slatify@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test_main (2.5) / unit
The following actions uses node12 which is deprecated and will be forced to run on node16: lazy-actions/slatify@master. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/