Skip to content
Future Java Compatibility Test

Future Java Compatibility Test #39

Sign in to view logs

Future Java Compatibility Test

Future Java Compatibility Test #39

Triggered via schedule August 17, 2024 02:39
@stas-panasiukstas-panasiuk
⁠ 6049872
develop
Status Failure
Total duration 11m 16s
Artifacts –

build_and_test_future_java.yml

on: schedule
build_and_test_java11
11m 7s
build_and_test_java11
build_and_test_java17
2m 43s
build_and_test_java17
build_and_test_java21
1m 55s
build_and_test_java21
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
build_and_test_java21
Process completed with exit code 1.
build_and_test_java17
Process completed with exit code 1.
build_and_test_java11
Process completed with exit code 1.
build_and_test_java21
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build_and_test_java17
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build_and_test_java11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/