Skip to content
integration-tests

chore(deps): update dependency pyopenssl to v25 #1726

Sign in to view logs

chore(deps): update dependency pyopenssl to v25

chore(deps): update dependency pyopenssl to v25 #1726

Triggered via pull request January 12, 2025 18:03
@renovaterenovate[bot]
opened #430
renovate/pyopenssl-25.x
Status Failure
Total duration 12h 47m 32s
Artifacts 18

integration_test.yaml

on: pull_request
Integration test with juju 3.1  /  Plan
3s
Integration test with juju 3.1 / Plan
Integration test using private-endpoint  /  Plan
6s
Integration test using private-endpoint / Plan
openstack interface test using private-endpoint  /  Plan
6s
openstack interface test using private-endpoint / Plan
Matrix: Integration test with juju 3.1 / build
Matrix: Integration test using private-endpoint / build
Matrix: openstack interface test using private-endpoint / build
Matrix: Integration test with juju 3.1 / Integration tests / Integration tests
Integration test with juju 3.1  /  Plan Image Scanning
2s
Integration test with juju 3.1 / Plan Image Scanning
Matrix: Integration test using private-endpoint / Integration tests / Integration tests
Integration test using private-endpoint  /  Plan Image Scanning
5s
Integration test using private-endpoint / Plan Image Scanning
Matrix: openstack interface test using private-endpoint / Integration tests / Integration tests
openstack interface test using private-endpoint  /  Plan Image Scanning
4s
openstack interface test using private-endpoint / Plan Image Scanning
Integration test with juju 3.1  /  Required Integration Test Status Checks
0s
Integration test with juju 3.1 / Required Integration Test Status Checks
Matrix: Integration test with juju 3.1 / scan
Integration test using private-endpoint  /  Required Integration Test Status Checks
0s
Integration test using private-endpoint / Required Integration Test Status Checks
Matrix: Integration test using private-endpoint / scan
openstack interface test using private-endpoint  /  Required Integration Test Status Checks
0s
openstack interface test using private-endpoint / Required Integration Test Status Checks
Matrix: openstack interface test using private-endpoint / scan
allure-report  /  Publish Allure report
allure-report / Publish Allure report
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 17 warnings
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_metrics_success)
Process completed with exit code 1.
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_metrics_failure)
The process '/usr/bin/sudo' failed with exit code 10
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_runner)
The process '/usr/bin/sudo' failed with exit code 10
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_repo)
Process completed with exit code 1.
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_fork_repo)
Process completed with exit code 1.
openstack interface test using private-endpoint / Integration tests / Integration tests (test_runner_manager_openstack)
Process completed with exit code 127.
openstack interface test using private-endpoint / Integration tests / Integration tests (test_runner_manager_openstack)
The process '/usr/bin/sudo' failed with exit code 10
openstack interface test using private-endpoint / Required Integration Test Status Checks
Process completed with exit code 1.
Integration test using private-endpoint / Integration tests / Integration tests (test_reactive)
The self-hosted runner: stg-gh-deploy-32-6c356fca9db708587fd3336f 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.
Integration test using private-endpoint / Integration tests / Integration tests (test_reactive)
The process '/usr/bin/sudo' failed with exit code 10
Integration test using private-endpoint / Required Integration Test Status Checks
Process completed with exit code 1.
Integration test with juju 3.1 / Integration tests / Integration tests (test_charm_scheduled_events)
Process completed with exit code 1.
Integration test with juju 3.1 / Integration tests / Integration tests (test_charm_scheduled_events)
Process completed with exit code 1.
Integration test with juju 3.1 / Integration tests / Integration tests (test_charm_upgrade)
Process completed with exit code 127.
Integration test with juju 3.1 / Integration tests / Integration tests (test_charm_upgrade)
The process '/usr/bin/sudo' failed with exit code 10
Integration test with juju 3.1 / Integration tests / Integration tests (test_debug_ssh)
Process completed with exit code 127.
Integration test with juju 3.1 / Integration tests / Integration tests (test_debug_ssh)
The process '/usr/bin/sudo' failed with exit code 10
Integration test with juju 3.1 / Required Integration Test Status Checks
Process completed with exit code 1.
Integration test with juju 3.1 / Plan
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test using private-endpoint / Plan
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
openstack interface test using private-endpoint / Plan
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test using private-endpoint / Build charm (github-runner)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
openstack interface test using private-endpoint / Build charm (github-runner)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test using private-endpoint / Plan Image Scanning
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
openstack interface test using private-endpoint / Plan Image Scanning
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test with juju 3.1 / Build charm (github-runner)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test with juju 3.1 / Plan Image Scanning
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_metrics_failure)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
Integration test using private-endpoint / Integration tests / Integration tests (test_charm_runner)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
openstack interface test using private-endpoint / Integration tests / Integration tests (test_runner_manager_openstack)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
openstack interface test using private-endpoint / Required Integration Test Status Checks
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test using private-endpoint / Required Integration Test Status Checks
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Integration test with juju 3.1 / Integration tests / Integration tests (test_charm_upgrade)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
Integration test with juju 3.1 / Integration tests / Integration tests (test_debug_ssh)
No files were found with the provided path: ./allure-results/. No artifacts will be uploaded.
Integration test with juju 3.1 / Required Integration Test Status Checks
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
2025-01-12T18-04-01-803a__build__output__charm__github-runner
28 MB
2025-01-12T18-04-01-803a__plan
298 Bytes
2025-01-12T18-04-03-9d16__build__output__charm__github-runner
28 MB
2025-01-12T18-04-03-9d16__plan
299 Bytes
2025-01-12T18-04-04-8189__build__output__charm__github-runner
28 MB
2025-01-12T18-04-04-8189__plan
298 Bytes
allure-fallback-results-0c85d275-3266-4008-8def-d2bb00710845-test_charm_scheduled_events
739 Bytes
allure-fallback-results-6eabbbe1-7c38-4593-ae33-5209fc54045e-test_charm_upgrade
561 Bytes
allure-fallback-results-b90406d4-6728-4d80-961b-b31588bc2fcf-test_debug_ssh
634 Bytes
allure-fallback-results-c3535b5d-8e06-464d-87ec-bb901819bd54-test_charm_fork_repo
666 Bytes
allure-fallback-results-cc9058ae-ae37-41ef-b373-dd347034a812-test_reactive
1.78 KB
allure-fallback-results-d1a8273b-d81f-49ae-9623-afd41962ee3f-test_charm_metrics_failure
1.34 KB
allure-fallback-results-dba21c9d-5a01-46a2-bf64-61d00fef57fb-test_charm_runner
1.93 KB
allure-fallback-results-e71f8986-f602-4347-8eee-5453d323467e-test_runner_manager_openstack
2.96 KB
allure-fallback-results-f9553cd5-c2ce-4244-9a00-c60db5ddd2bc-test_charm_metrics_success
1.26 KB
allure-results-0c85d275-3266-4008-8def-d2bb00710845-test_charm_scheduled_events
13.4 KB
allure-results-c3535b5d-8e06-464d-87ec-bb901819bd54-test_charm_fork_repo
14.5 KB
allure-results-f9553cd5-c2ce-4244-9a00-c60db5ddd2bc-test_charm_metrics_success
19.1 KB