Skip to content
Build

python-libnvme: drop 1.x backward-compatibility shims #4096

Sign in to view logs

python-libnvme: drop 1.x backward-compatibility shims

python-libnvme: drop 1.x backward-compatibility shims #4096

Triggered via pull request March 24, 2026 16:39
@martin-belangermartin-belanger
opened #3205
martin-belanger:python-cleanup
Status Failure
Total duration 1m 35s
Artifacts 2

build.yml

on: pull_request
fallback shared libraries
fallback shared libraries
muon minimal static
36s
muon minimal static
make static
48s
make static
musl libc build on Debian
33s
musl libc build on Debian
musl libc minimal static build on Debian
33s
musl libc minimal static build on Debian
musl libc build on Alpine
42s
musl libc build on Alpine
build libnvme and nvme-cli separately
57s
build libnvme and nvme-cli separately
Matrix: cross
Matrix: libnvme
Matrix: nvme-cli
Fit to window
Zoom out
Zoom in

Annotations

27 errors
nvme-cli (fedora, clang, debug)
Process completed with exit code 1.
nvme-cli (debian, clang, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (debian, clang, debug)
The operation was canceled.
nvme-cli (tumbleweed, clang, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, clang, debug)
The operation was canceled.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, clang, release)
The operation was canceled.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (debian, gcc, release)
The operation was canceled.
nvme-cli (fedora, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (fedora, gcc, debug)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
nvme-cli (fedora, gcc, debug)
Process completed with exit code 1.
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (fedora, clang, release)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
nvme-cli (fedora, clang, release)
Process completed with exit code 1.
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (debian, gcc, debug)
The operation was canceled.
nvme-cli (tumbleweed, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, gcc, release)
The operation was canceled.
nvme-cli (fedora, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (fedora, gcc, release)
The operation was canceled.
libnvme (debian, gcc, release)
Process completed with exit code 1.
nvme-cli (debian, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (debian, clang, release)
The operation was canceled.
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, gcc, debug)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
nvme-cli (tumbleweed, gcc, debug)
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
19.6 KB
sha256:c2339a0f6b681263c640a4389181199f590e65c73b9db28766c3df064f5e8ea3
logs files
17.6 KB
sha256:552bea4ff68becab7646379a74d55300be074a05fa42cf82fa382bc73e42ca36