Skip to content

fix: shared conn data race and FVT tests #11519

fix: shared conn data race and FVT tests

fix: shared conn data race and FVT tests #11519

Triggered via pull request April 23, 2026 07:40
Status Cancelled
Total duration 1m 57s
Artifacts

run_test_case.yaml

on: pull_request
run_unit_tests
1m 23s
run_unit_tests
run_fvt_tests  /  fvt_tests_with_edgex
1m 27s
run_fvt_tests / fvt_tests_with_edgex
run_fvt_tests  /  fvt_tests_redis_as_storage
1m 30s
run_fvt_tests / fvt_tests_redis_as_storage
run_fvt_tests  /  fvt_tests_for_container_in_helm
1m 22s
run_fvt_tests / fvt_tests_for_container_in_helm
upload_coverage
0s
upload_coverage
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 8 warnings
run_unit_tests
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
run_unit_tests
The operation was canceled.
run_fvt_tests / fvt_tests_for_container_in_helm
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
run_fvt_tests / fvt_tests_for_container_in_helm
The operation was canceled.
run_fvt_tests / fvt_tests_with_edgex
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
run_fvt_tests / fvt_tests_with_edgex
Input required and not supplied: path
run_fvt_tests / fvt_tests_with_edgex
The operation was canceled.
run_fvt_tests / fvt_tests_redis_as_storage
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
run_fvt_tests / fvt_tests_redis_as_storage
Input required and not supplied: path
run_fvt_tests / fvt_tests_redis_as_storage
The operation was canceled.
Run test cases
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
Run test cases
Canceling since a higher priority waiting request for test-pull_request-refs/pull/4032/merge exists
run_unit_tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/setup-python@v5. 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/
run_fvt_tests / fvt_tests_for_container_in_helm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@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/
run_fvt_tests / fvt_tests_with_edgex
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/setup-java@v4, 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/
run_fvt_tests / fvt_tests_with_edgex
No files were found with the provided path: ./jmeter_logs. No artifacts will be uploaded.
run_fvt_tests / fvt_tests_with_edgex
Restore cache failed: Dependencies file is not found in /home/runner/work/ekuiper/ekuiper. Supported file pattern: go.sum
run_fvt_tests / fvt_tests_redis_as_storage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/setup-java@v4, 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/
run_fvt_tests / fvt_tests_redis_as_storage
No files were found with the provided path: ./jmeter_logs. No artifacts will be uploaded.
run_fvt_tests / fvt_tests_redis_as_storage
Restore cache failed: Dependencies file is not found in /home/runner/work/ekuiper/ekuiper. Supported file pattern: go.sum