Skip to content

Fixes #37158: Explicitly define upgrade steps in upgrade scenario #1132

Fixes #37158: Explicitly define upgrade steps in upgrade scenario

Fixes #37158: Explicitly define upgrade steps in upgrade scenario #1132

Triggered via pull request September 14, 2023 02:03
Status Failure
Total duration 1m 1s
Artifacts

ruby_tests.yml

on: pull_request
Matrix: Test_ruby
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Test_ruby (3.2.1)
Process completed with exit code 1.
Test_ruby (3.1.3)
Process completed with exit code 1.
Test_ruby (3.0.2)
Process completed with exit code 1.
Test_ruby (2.7.4)
Process completed with exit code 1.
Test_ruby (3.2.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test_ruby (3.1.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test_ruby (3.0.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test_ruby (2.7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/