integration-tests #216
cbartzintegration_test.yaml
on: schedule
Cross controller integration test using private-endpoint
/
Plan
11s
Integration test using private-endpoint
/
Plan
8s
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
0s
Integration test using private-endpoint
/
Plan Image Scanning
0s
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
Integration test using private-endpoint
/
Required Integration Test Status Checks
0s
allure-report
/
Publish Allure report
Annotations
19 errors and 8 warnings
|
Integration test using private-endpoint / Build charm (github-runner)
The process '/snap/bin/charmcraft' failed with exit code 70
|
|
Cross controller integration test using private-endpoint / Build charm (github-runner)
The process '/snap/bin/charmcraft' failed with exit code 70
|
|
Runner tests across bases (24.04) / Build charm (github-runner)
The process '/snap/bin/charmcraft' failed with exit code 70
|
|
Runner tests across bases (22.04) / Build charm (github-runner)
The process '/snap/bin/charmcraft' failed with exit code 70
|
|
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_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_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_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
|
|
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
|
|
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-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 (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/
|
|
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 / 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) / 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) / 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
2026-04-01T18-15-52-811e__plan
|
298 Bytes |
sha256:c10112762ad15c47fbbbc5a0c736896e8e40245a2fd2b37b9e714d1beb503c1c
|
|
|
2026-04-01T18-15-53-9f5b__plan
|
300 Bytes |
sha256:6cf85445c5bb0ec142ea6214347d504e2835fc951abbb58bc896021a29baf3e4
|
|
|
2026-04-01T18-15-53-abe4__plan
|
299 Bytes |
sha256:b76d546acc68573b3c970d302a5b7ddd27224125fb46a03a677dfc1f6d746a3a
|
|
|
2026-04-01T18-15-54-b374__plan
|
299 Bytes |
sha256:47826a77900db12691935fcdd38b57700bd2f7bdbba9b681f09b2445bfbba2bb
|
|