Skip to content
Test

fix: non-zero exit code in RDMA naming script #516

Sign in to view logs

fix: non-zero exit code in RDMA naming script

fix: non-zero exit code in RDMA naming script #516

Triggered via pull request March 24, 2026 09:58
@ggoklaniggoklani
opened #110
ggoklani:fix_rdma_naming_script_new
Status Success
Total duration 9m 16s
Artifacts –

qemu-kvm-integration-tests.yml

on: pull_request
Matrix: scenario
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
scenario (centos-10, qemu-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (centos-10-bootc, container-ansible-core-2-17)
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
scenario (fedora-43-bootc, container-ansible-core-2-20)
Ignoring the PR from a forked repository
scenario (fedora-42, qemu-ansible-core-2-19)
Ignoring the PR from a forked repository
scenario (fedora-43, qemu-ansible-core-2-20)
Ignoring the PR from a forked repository
scenario (leap-15.6, qemu-ansible-core-2-18)
Ignoring the PR from a forked repository
scenario (fedora-42-bootc, container-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (fedora-42, container-ansible-core-2-17)
Ignoring the PR from a forked repository
scenario (centos-9-bootc, container-ansible-core-2-16)
Ignoring the PR from a forked repository