Skip to content
GraalVM Latest CI

Fix getting an exception #1053

Sign in to view logs

Fix getting an exception

Fix getting an exception #1053

Triggered via pull request November 22, 2024 11:29
@sdelamosdelamo
synchronize #883
fixxes
Status Success
Total duration 4h 30m 28s
Artifacts –

graalvm-latest.yml

on: pull_request
build_matrix
3m 33s
build_matrix
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build_matrix
The following actions use a deprecated Node.js version and will be forced to run on node20: gradle/gradle-build-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (17, test-suite:micronaut-serialization:nativeTest)
This build uses the last update of Oracle GraalVM for JDK 17 under the GFTC. More details: https://github.com/marketplace/actions/github-action-for-graalvm#notes-on-oracle-graalvm-for-jdk-17
build (17, test-suite:micronaut-serialization:nativeTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: gradle/gradle-build-action@v2, mikepenz/action-junit-report@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 (21, test-suite:micronaut-serialization:nativeTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: gradle/gradle-build-action@v2, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/