Skip to content
Gradle Check

Use JUnit timeouts instead of Jagr #23

Sign in to view logs

Use JUnit timeouts instead of Jagr

Use JUnit timeouts instead of Jagr #23

Triggered via push December 13, 2023 09:18
@zentoxzentox
pushed e82457e
master
Status Success
Total duration 2m 44s
Artifacts –

gradle-check.yml

on: push
Matrix: gradle_check
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Check on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-java@v2, gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-java@v2, gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-java@v2, gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/