Skip to content

(maint) see if apply integration can run on ruby 3.2 #481

(maint) see if apply integration can run on ruby 3.2

(maint) see if apply integration can run on ruby 3.2 #481

Triggered via pull request May 23, 2024 22:14
Status Failure
Total duration 6m 22s
Artifacts

apply.yaml

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

Annotations

11 errors and 2 warnings
Tests (windows-latest, 3.2)
Process completed with exit code 1.
Tests (windows-latest, 2.7)
The job was canceled because "windows-latest_3_2" failed.
Tests (windows-latest, 2.7)
The operation was canceled.
Tests (windows-latest, 3.1)
The job was canceled because "windows-latest_3_2" failed.
Tests (windows-latest, 3.1)
The operation was canceled.
Tests (ubuntu-latest, 3.2)
The job was canceled because "windows-latest_3_2" failed.
Tests (ubuntu-latest, 3.2)
The operation was canceled.
Tests (ubuntu-latest, 3.1)
The job was canceled because "windows-latest_3_2" failed.
Tests (ubuntu-latest, 3.1)
The operation was canceled.
Tests (ubuntu-latest, 2.7)
The job was canceled because "windows-latest_3_2" failed.
Tests (ubuntu-latest, 2.7)
The operation was canceled.
Tests (windows-latest, 3.2)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Tests (windows-latest, 3.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/