Skip to content

test: refactor test setup to add device info #260

test: refactor test setup to add device info

test: refactor test setup to add device info #260

Triggered via pull request April 30, 2026 20:32
Status Failure
Total duration 2h 12m 25s
Artifacts 3
Matrix: scenario
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 8 warnings
scenario (centos-9, qemu-ansible-core-2-16)
Process completed with exit code 1.
scenario (centos-10, qemu-ansible-core-2-17)
Process completed with exit code 1.
scenario (fedora-43, qemu-ansible-core-2-20)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
scenario (fedora-42, qemu-ansible-core-2-19)
Process completed with exit code 1.
scenario (fedora-42, container-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (fedora-43-bootc, container-ansible-core-2-20)
Ignoring the PR from a forked repository
scenario (centos-9-bootc, container-ansible-core-2-16)
Ignoring the PR from a forked repository
scenario (centos-10-bootc, container-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (fedora-42-bootc, container-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (leap-15.6, qemu-ansible-core-2-18)
Ignoring the PR from a forked repository
scenario (centos-9, container-ansible-core-2-16)
Ignoring the PR from a forked repository
scenario (fedora-43, container-ansible-core-2-20)
Ignoring the PR from a forked repository

Artifacts

Produced during runtime
Name Size Digest
logs-centos-10-qemu-ansible-core-2-17
4.43 MB
sha256:eb78b53c3c180215a14c8eb5d2f5c32260551aa7245f7e5d4a07f5ac1d882edc
logs-centos-9-qemu-ansible-core-2-16
4.18 MB
sha256:5ff0703835c0cb93997a54492d3439dfc67be9ab0a3818d7f49bbc772e961d28
logs-fedora-42-qemu-ansible-core-2-19
4.34 MB
sha256:761bb5e4d8126c869dd8886daadc444b82713e74bdca7ad7cebab090b7f9a8cc