Skip to content

integration-tests

integration-tests #268

Triggered via schedule April 27, 2026 18:21
Status Cancelled
Total duration 1d 0h 1m 33s
Artifacts 8

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
10s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
6s
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
3s
Cross controller integration test using private-endpoint / Plan Image Scanning
Integration test using private-endpoint  /  Plan Image Scanning
4s
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
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_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_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_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_charm_metrics_success)
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
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
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
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-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
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/
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/
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/
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/
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/
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-27T18-22-32-b91f__build__output__charm__github-runner
55.5 MB
sha256:d287b4497ce6a125459e0c28fedd2e6741cdd430e09f8fa0c64587a91964572b
2026-04-27T18-22-32-b91f__plan
299 Bytes
sha256:48647f7425f2fee9cb18f88c00cbf06eb7ff955a3fff060e3da30ab68d05fa03
2026-04-27T18-22-34-a6dc__build__output__charm__github-runner
55.5 MB
sha256:d9457eb0ab331d7da8d7a05014c946745da3599619ae4163275b5654fa42e291
2026-04-27T18-22-34-a6dc__plan
299 Bytes
sha256:72779428b8320df8fd6fbb1bbdbe9d8193dc4c8dfdba378a2318bdd553014de5
2026-04-27T18-22-35-82d4__build__output__charm__github-runner
55.4 MB
sha256:6a0f0f1846eac3fdc29b1eee4cdfd75a38897d0653f6f598fcb08ff2783b59fa
2026-04-27T18-22-35-82d4__plan
299 Bytes
sha256:e06a9bc3eb42e01af9535cc579770384f3c01f4665f350bf0a8e6755f4fa9bc1
2026-04-27T18-22-37-b701__build__output__charm__github-runner
55.5 MB
sha256:a307c439f76afb13c91b0feb3de1e4997ed1e6cd5e0e70592c4beb0e67eebeb9
2026-04-27T18-22-37-b701__plan
299 Bytes
sha256:70278b9d79d05e32c9f93851e1f48518110292291389071a9ec671016a4c067e