Skip to content

edge_orchestrator CI on branch >> 137/merge << #635

edge_orchestrator CI on branch >> 137/merge <<

edge_orchestrator CI on branch >> 137/merge << #635

Triggered via pull request April 3, 2026 12:56
Status Failure
Total duration 1m 9s
Artifacts

ci_edge_orchestrator.yml

on: pull_request
Matrix: Run Python linter and tests (unit > integration > functional)
Matrix: build_and_push_images
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 12 warnings
Run Python linter and tests (unit > integration > functional) (3.10)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.10)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.10)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.10)
Process completed with exit code 2.
Run Python linter and tests (unit > integration > functional) (3.11)
The strategy configuration was canceled because "lint_and_test_on_edge_orchestrator._3_10" failed
Run Python linter and tests (unit > integration > functional) (3.11)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.11)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.11)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.11)
Process completed with exit code 2.
Run Python linter and tests (unit > integration > functional) (3.9)
The strategy configuration was canceled because "lint_and_test_on_edge_orchestrator._3_10" failed
Run Python linter and tests (unit > integration > functional) (3.9)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.9)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.9)
No test report files were found
Run Python linter and tests (unit > integration > functional) (3.9)
The operation was canceled.
Run Python linter and tests (unit > integration > functional) (3.10)
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-python@v5, dorny/test-reporter@v1. 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 Python linter and tests (unit > integration > functional) (3.10)
No file matches path edge/orchestrator/reports/behave/*.xml
Run Python linter and tests (unit > integration > functional) (3.10)
No file matches path edge/orchestrator/reports/pytest/integration-tests-report.xml
Run Python linter and tests (unit > integration > functional) (3.10)
No file matches path edge/orchestrator/reports/pytest/unit-tests-report.xml
Run Python linter and tests (unit > integration > functional) (3.11)
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-python@v5, dorny/test-reporter@v1. 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 Python linter and tests (unit > integration > functional) (3.11)
No file matches path edge/orchestrator/reports/behave/*.xml
Run Python linter and tests (unit > integration > functional) (3.11)
No file matches path edge/orchestrator/reports/pytest/integration-tests-report.xml
Run Python linter and tests (unit > integration > functional) (3.11)
No file matches path edge/orchestrator/reports/pytest/unit-tests-report.xml
Run Python linter and tests (unit > integration > functional) (3.9)
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-python@v5, dorny/test-reporter@v1. 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 Python linter and tests (unit > integration > functional) (3.9)
No file matches path edge/orchestrator/reports/behave/*.xml
Run Python linter and tests (unit > integration > functional) (3.9)
No file matches path edge/orchestrator/reports/pytest/integration-tests-report.xml
Run Python linter and tests (unit > integration > functional) (3.9)
No file matches path edge/orchestrator/reports/pytest/unit-tests-report.xml