Skip to content

integration-tests

integration-tests #238

Triggered via schedule April 12, 2026 18:07
Status Cancelled
Total duration 1d 0h 11m 13s
Artifacts 8

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
6s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
8s
Integration test using private-endpoint / Plan
Matrix: Runner tests across bases
Matrix: Cross controller integration test using private-endpoint / build
Matrix: Cross controller integration test using private-endpoint / Integration tests / Integration tests
Matrix: Integration test using private-endpoint / build
Matrix: Integration test using private-endpoint / Integration tests / Integration tests
Cross controller integration test using private-endpoint  /  Plan Image Scanning
8s
Cross controller integration test using private-endpoint / Plan Image Scanning
Integration test using private-endpoint  /  Plan Image Scanning
5s
Integration test using private-endpoint / Plan Image Scanning
Matrix: Cross controller integration test using private-endpoint / scan
Matrix: Integration test using private-endpoint / scan
Cross controller integration test using private-endpoint  /  Required Integration Test Status Checks
0s
Cross controller integration test using private-endpoint / Required Integration Test Status Checks
Integration test using private-endpoint  /  Required Integration Test Status Checks
Integration test using private-endpoint / Required Integration Test Status Checks
allure-report  /  Publish Allure report
allure-report / Publish Allure report
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 12 warnings
Runner tests across bases (22.04) / Integration tests / Integration tests (test_charm_runner)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Cross controller integration test using private-endpoint / Integration tests / Integration tests (test_prometheus_metrics)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_upgrade)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_path_change)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_reactive)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_multi_unit_same_machine)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Runner tests across bases (24.04) / Integration tests / Integration tests (test_charm_runner)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_no_runner)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_metrics_failure)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_metrics_success)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
integration-tests
Canceling since a higher priority waiting request for integration-tests-refs/heads/main exists
integration-tests
Canceling since a higher priority waiting request for integration-tests-refs/heads/main exists
integration-tests
Canceling since a higher priority waiting request for integration-tests-refs/heads/main exists
integration-tests
Canceling since a higher priority waiting request for integration-tests-refs/heads/main exists
integration-tests
Canceling since a higher priority waiting request for integration-tests-refs/heads/main exists
Runner tests across bases (22.04) / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Cross controller integration test using private-endpoint / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Integration test using private-endpoint / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Runner tests across bases (24.04) / Plan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan@main. 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/
Cross controller integration test using private-endpoint / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Cross controller integration test using private-endpoint / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Runner tests across bases (24.04) / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Runner tests across bases (24.04) / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Integration test using private-endpoint / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Integration test using private-endpoint / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/
Runner tests across bases (22.04) / Build charm (github-runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/build@main. 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/
Runner tests across bases (22.04) / Plan Image Scanning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: canonical/operator-workflows/internal/plan-scan@main. 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/

Artifacts

Produced during runtime
Name Size Digest
2026-04-12T18-18-42-bb5c__build__output__charm__github-runner
55.4 MB
sha256:bc8f805b65de2ad2a921d6e08be1dfc30b55ffe59c92b193d8027495433a9069
2026-04-12T18-18-42-bb5c__plan
298 Bytes
sha256:5567d87bb34694b188d5782afc98d5b416f9235fad8c6ceb5a3deb49cc7ef7fb
2026-04-12T18-18-42-bb94__build__output__charm__github-runner
55.4 MB
sha256:6c3dee0b8957ebb603a70956d757626b09282044a54f02603a5a80365637a593
2026-04-12T18-18-42-bb94__plan
298 Bytes
sha256:86bfcec7bc7a6cb302f4dcad6d849dffd676dc2dc3695ab0fa139d4e47af06f9
2026-04-12T18-18-44-a02d__build__output__charm__github-runner
55.4 MB
sha256:9305435b60aa5a1f5981c5abc52ce70a1c43e675bcfaf0d29c29e7b66f30e59e
2026-04-12T18-18-44-a02d__plan
298 Bytes
sha256:d3ffda5b8799c137498285ef4b5b513e9acd053d634e48a85d2fe95022717409
2026-04-12T18-18-44-b559__build__output__charm__github-runner
55.4 MB
sha256:1bb2eb2ec6861572fda410b8509ed127c1fdf793afc103e195df1efd52039776
2026-04-12T18-18-44-b559__plan
299 Bytes
sha256:39d932da654de54d05ba322e66c9afafbacf44d366f77adb5a7587994fc0be78