Skip to content

[jnigen] Fix flaky tests (#814) #27

[jnigen] Fix flaky tests (#814)

[jnigen] Fix flaky tests (#814) #27

Re-run triggered November 21, 2023 11:45
Status Success
Total duration 2m 51s
Artifacts

jnigen.yaml

on: push
Matrix: analyze_jnigen
build_jni_example_linux
1m 34s
build_jni_example_linux
build_jni_example_windows
4m 30s
build_jni_example_windows
build_jni_example_android
3m 10s
build_jni_example_android
run_pdfbox_example_linux
2m 50s
run_pdfbox_example_linux
Matrix: test_jnigen
test_jnigen_windows_minimal
8m 56s
test_jnigen_windows_minimal
test_jnigen_macos_minimal
5m 37s
test_jnigen_macos_minimal
test_jni_windows_minimal
3m 45s
test_jni_windows_minimal
test_jni_macos_minimal
2m 33s
test_jni_macos_minimal
coveralls_finish
6s
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/