Skip to content

Add integration tests for ELK Analytics enabled with an operation policy #2228

Add integration tests for ELK Analytics enabled with an operation policy

Add integration tests for ELK Analytics enabled with an operation policy #2228

Triggered via pull request January 12, 2024 05:59
Status Cancelled
Total duration 20s
Artifacts

maven.yml

on: pull_request
Matrix: build
run-benchmark-test
11s
run-benchmark-test
show-report
0s
show-report
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
build (2, group2)
Process completed with exit code 1.
build (1, group1)
Process completed with exit code 1.
build (1, group1)
The operation was canceled.
build (2, group2)
The operation was canceled.
run-benchmark-test
The operation was canceled.
build (1, group1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1, group1)
No files were found with the provided path: TEST-TestSuite_1.xml. No artifacts will be uploaded.
build (2, group2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2, group2)
No files were found with the provided path: TEST-TestSuite_2.xml. No artifacts will be uploaded.
run-benchmark-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/