Skip to content

jnigen

jnigen #9

Triggered via schedule November 19, 2023 00:09
Status Success
Total duration 11m 37s
Artifacts

jnigen.yaml

on: schedule
Matrix: analyze_jnigen
analyze_jni
48s
analyze_jni
build_jni_example_linux
1m 42s
build_jni_example_linux
build_jni_example_windows
5m 39s
build_jni_example_windows
build_jni_example_android
3m 36s
build_jni_example_android
run_pdfbox_example_linux
2m 35s
run_pdfbox_example_linux
Matrix: test_jnigen
test_jnigen_windows_minimal
10m 38s
test_jnigen_windows_minimal
test_jnigen_macos_minimal
5m 12s
test_jnigen_macos_minimal
test_jni_windows_minimal
4m 33s
test_jni_windows_minimal
test_jni_macos_minimal
2m 47s
test_jni_macos_minimal
coveralls_finish
7s
coveralls_finish
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
analyze_jnigen (stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: axel-op/googlejavaformat-action@fe78db8a90171b6a836449f8d0e982d5d71e5c5a. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
analyze_jni
The following actions uses node12 which is deprecated and will be forced to run on node16: axel-op/googlejavaformat-action@fe78db8a90171b6a836449f8d0e982d5d71e5c5a. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/