Skip to content

integration-tests

integration-tests #262

Triggered via schedule April 24, 2026 18:10
Status Cancelled
Total duration 1d 0h 11m 58s
Artifacts 8

integration_test.yaml

on: schedule
Cross controller integration test using private-endpoint  /  Plan
7s
Cross controller integration test using private-endpoint / Plan
Integration test using private-endpoint  /  Plan
5s
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
5s
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 (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_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
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_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_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
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 (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/
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
2026-04-24T18-21-50-8fa6__build__output__charm__github-runner
55.4 MB
sha256:12dc6870dd624d455105b9bb91e58a3463e5794c1b161952c387ede80df588dd
2026-04-24T18-21-50-8fa6__plan
299 Bytes
sha256:a68ca7ad5730a32643c42e5f298ac0eadcf21d6f90903260f6695cd61a6f631d
2026-04-24T18-21-50-93d5__build__output__charm__github-runner
55.4 MB
sha256:eaebc3c719209000c64af6d7c1cd5af79d0079251aca0e22a48281c4f4731e80
2026-04-24T18-21-50-93d5__plan
299 Bytes
sha256:374ba982073451b7e4327e3e55d9626c209fae2b97def162e4a77cd82c13259f
2026-04-24T18-21-51-badb__build__output__charm__github-runner
55.4 MB
sha256:553683f2b243f5e56913915200257ea8d60d03b45af1b9d5a15f1210cc1f4b5c
2026-04-24T18-21-51-badb__plan
299 Bytes
sha256:a81e490b4bdc9abeacaa92733c922fb0d64d32c21cd8a6af4ffa18de8509dd21
2026-04-24T18-21-53-b45f__build__output__charm__github-runner
55.4 MB
sha256:b7bf1d0fc80717dcd1212117e1ed134a4748ed4fc845fb70c950a805b57d84fa
2026-04-24T18-21-53-b45f__plan
299 Bytes
sha256:a705ca60912bb7fad3a85b7d53b946ca848351b365f649e90d5cd11d85d205c3