Skip to content

Temporarily disable cached builds (#514) #305

Temporarily disable cached builds (#514)

Temporarily disable cached builds (#514) #305

Triggered via push November 11, 2024 15:26
Status Failure
Total duration 1h 35m 9s
Artifacts 16

release.yaml

on: push
Matrix: ci-tests / Build charm
Build charm  /  Collect bases for charm | .
16s
Build charm / Collect bases for charm | .
ci-tests  /  ...  /  Lint .github/workflows/
3s
ci-tests / Lint / Lint .github/workflows/
ci-tests  /  ...  /  tox run -e lint
20s
ci-tests / Lint / tox run -e lint
ci-tests  /  Unit test charm
5m 13s
ci-tests / Unit test charm
ci-tests  /  Check libraries
36s
ci-tests / Check libraries
ci-tests  /  Check Terraform
5s
ci-tests / Check Terraform
Matrix: Build charm / build
Matrix: ci-tests / integration-test
Release charm  /  Release charm
Release charm / Release charm
Release libraries
0s
Release libraries
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
ci-tests / Integration test charm | 3.5.3 / tls_tests/test_tls.py | group 1
Process completed with exit code 1.
ci-tests / Integration test charm | 3.5.3 / test_charm.py | group 1
The self-hosted runner: openstack-amd64-large-ps6-3-44356445f1eb59afd8854186 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci-tests / Integration test charm | 3.5.3 / sharding_tests/test_sharding.py | group 1
The self-hosted runner: openstack-amd64-large-ps6-2-d1627b29e413742352b1e4a7 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci-tests / Integration test charm | 3.5.3 / upgrade/test_upgrade.py | group 1
The self-hosted runner: openstack-amd64-large-ps6-2-f9895411289c9e793fae15b4 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
ci-tests / Check libraries
The following actions use a deprecated Node.js version and will be forced to run on node20: canonical/charming-actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
logs-integration-test-charm-lxd-juju-3.5.3-amd64-backup_tests-test_backups.py-group-1
290 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-ha_tests-test_ha.py-group-1
261 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-metrics_tests-test_metrics.py-group-1
60.4 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-relation_tests-new_relations-test_charm_relations.py-group-1
178 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-sharding_tests-test_mongos.py-group-1
43.3 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-sharding_tests-test_sharding_backups.py-group-1
494 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-sharding_tests-test_sharding_race_conds.py-group-1
372 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-sharding_tests-test_sharding_relations.py-group-1
54.7 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-sharding_tests-test_sharding_tls.py-group-1
1.03 MB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-tls_tests-test_tls.py-group-1
207 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-upgrade-test_sharding_rollback.py-group-1
466 KB
logs-integration-test-charm-lxd-juju-3.5.3-amd64-upgrade-test_sharding_upgrade.py-group-1
895 KB
packed-charm-cache-false-.-base-0
32.5 MB
packed-charm-cache-false-tests-integration-relation_tests-new_relations-application-charm-base-0
5 MB
packed-charm-cache-false-tests-integration-sharding_tests-application-base-0
5.67 MB
temp-release-packed-charm-base-0
32.5 MB