[pull] master from ruby:master #437
Triggered via pull request
March 14, 2026 23:54
pull[bot]
Status
Cancelled
Total duration
1d 23h 20m 54s
Artifacts
–
test.yml
on: pull_request
ruby-versions
/
Generate Ruby versions
3s
Matrix: prism-version-test
Matrix: test
Annotations
22 errors and 10 warnings
|
test (3.0, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (4.0, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (head, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (jruby, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (truffleruby, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (4.0, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.1, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.3, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.3, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (jruby, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.3, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.1, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (jruby-head, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (head, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (jruby-head, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (head, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (4.0, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (mswin, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.2, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.4, ubuntu-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (truffleruby, macos-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
test (3.4, windows-latest)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
prism-version-test (1.0.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
prism-version-test (1.7.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.4, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
prism-version-test (1.3.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
prism-version-test (head)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.2, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.1, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.0, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.2, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test (3.0, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@6ca151fd1bfcfd6fe0c4eb6837eb0584d0134a0c. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|