[jnigen] Fix flaky tests #20
Triggered via pull request
November 20, 2023 16:07
HosseinYousefi
Status
Failure
Total duration
11m 50s
Artifacts
–
jnigen.yaml
on: pull_request
Matrix: analyze_jnigen
analyze_jni
55s
build_jni_example_linux
1m 24s
build_jni_example_windows
3m 55s
build_jni_example_android
3m 7s
run_pdfbox_example_linux
2m 40s
Matrix: test_jnigen
test_jnigen_windows_minimal
10m 57s
test_jnigen_macos_minimal
8m 13s
test_jni_windows_minimal
7m 38s
test_jni_macos_minimal
2m 28s
coveralls_finish
0s
Annotations
2 errors and 2 warnings
|
test_jni
154 tests passed, 1 failed.
|
|
test_jni
Process completed with exit code 255.
|
|
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/
|