Skip to content

integration-tests

integration-tests #278

Triggered via schedule May 2, 2026 18:12
Status Cancelled
Total duration 1d 0h 12m 5s
Artifacts 8

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
9s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
9s
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
6s
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
0s
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 (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_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_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_multi_unit_same_machine)
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
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_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_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_charm_metrics_success)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
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
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 (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/
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/
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/
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/
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/
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/
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/
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
2026-05-02T18-24-31-930c__build__output__charm__github-runner
55.5 MB
sha256:314047a23f9b5535727726474377da0e863eb78ab1e44feb2091ba151ff624aa
2026-05-02T18-24-31-930c__plan
300 Bytes
sha256:8b5b7a057871b654bf10aa2b9a1f38c143403364b6d4987670bc1db8253fa3d2
2026-05-02T18-24-31-b856__build__output__charm__github-runner
55.5 MB
sha256:0c646482c4b03e2689893ac1401fc5bbc99eff8dc16a71fc3db029f268a09b0d
2026-05-02T18-24-31-b856__plan
298 Bytes
sha256:8c1f40375b87cf38517b9c61759a5290b7d86acd4a93ed5aba8d1dc317725f8d
2026-05-02T18-24-32-a632__build__output__charm__github-runner
55.5 MB
sha256:ccd1edaf2ca5da0bf29032343f9c4bf4fc50bf0697c63e6d8da06a53238249b0
2026-05-02T18-24-32-a632__plan
299 Bytes
sha256:94cfdcfacbb055022678a1c051b845ba7bb575bb4efde4c0fe4e691a29822eb4
2026-05-02T18-24-32-b471__build__output__charm__github-runner
55.5 MB
sha256:6273e2ebf6f5e580bb8e5819dec58fc4d7a15ff0d947e11281277bf17b3bbe9b
2026-05-02T18-24-32-b471__plan
299 Bytes
sha256:40e4074808917046d6544c6d5ffd69f8e414e9287406f8a6c1c0d894cbb4e852