Skip to content

Improve API Provider Test Cases #3638

Improve API Provider Test Cases

Improve API Provider Test Cases #3638

Triggered via pull request April 21, 2026 16:46
Status Cancelled
Total duration 18m 46s
Artifacts

maven.yml

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

Annotations

15 errors and 9 warnings
build (4, group4)
Canceling since a higher priority waiting request for 14168 exists
build (4, group4)
Process completed with exit code 1.
build (4, group4)
The operation was canceled.
build (1, group1)
Canceling since a higher priority waiting request for 14168 exists
build (1, group1)
Process completed with exit code 1.
build (1, group1)
The operation was canceled.
build (2, group2)
Canceling since a higher priority waiting request for 14168 exists
build (2, group2)
Process completed with exit code 1.
build (2, group2)
The operation was canceled.
run-benchmark-test
Canceling since a higher priority waiting request for 14168 exists
run-benchmark-test
The operation was canceled.
build (3, group3)
Canceling since a higher priority waiting request for 14168 exists
build (3, group3)
Process completed with exit code 1.
build (3, group3)
The operation was canceled.
APIM builder
Canceling since a higher priority waiting request for 14168 exists
build (4, group4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v2, actions/setup-node@v1, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (4, group4)
No files were found with the provided path: TEST-TestSuite_4.xml. No artifacts will be uploaded.
build (1, group1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v2, actions/setup-node@v1, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (1, group1)
No files were found with the provided path: TEST-TestSuite_1.xml. No artifacts will be uploaded.
build (2, group2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v2, actions/setup-node@v1, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (2, group2)
No files were found with the provided path: TEST-TestSuite_2.xml. No artifacts will be uploaded.
run-benchmark-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v2, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3, group3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v2, actions/setup-node@v1, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3, group3)
No files were found with the provided path: TEST-TestSuite_3.xml. No artifacts will be uploaded.