Skip to content

id-ctrl: Add NVMe 2.3 id controller fields #3981

id-ctrl: Add NVMe 2.3 id controller fields

id-ctrl: Add NVMe 2.3 id controller fields #3981

Triggered via pull request March 12, 2026 18:24
Status Failure
Total duration 58s
Artifacts 3

build.yml

on: pull_request
fallback shared libraries
0s
fallback shared libraries
muon minimal static
46s
muon minimal static
make static
47s
make static
musl libc build on Debian
34s
musl libc build on Debian
musl libc build on Alpine
44s
musl libc build on Alpine
build libnvme and nvme-cli separately
45s
build libnvme and nvme-cli separately
Matrix: cross
Matrix: libnvme
Matrix: nvme-cli
Fit to window
Zoom out
Zoom in

Annotations

33 errors
musl libc build on Debian
Process completed with exit code 1.
cross (armhf)
Process completed with exit code 1.
cross (s390x)
The strategy configuration was canceled because "cross.armhf" failed
cross (s390x)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
cross (s390x)
Process completed with exit code 1.
cross (ppc64le)
The strategy configuration was canceled because "cross.armhf" failed
cross (ppc64le)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
cross (ppc64le)
Process completed with exit code 1.
nvme-cli (debian, clang, debug)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (fedora, gcc, debug)
Process completed with exit code 1.
musl libc build on Alpine
Process completed with exit code 1.
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (fedora, clang, release)
A task was canceled.
nvme-cli (tumbleweed, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (tumbleweed, gcc, release)
The operation was canceled.
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
muon minimal static
Process completed with exit code 1.
nvme-cli (debian, gcc, debug)
The operation was canceled.
nvme-cli (fedora, clang, debug)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (fedora, clang, debug)
The operation was canceled.
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (tumbleweed, gcc, debug)
The operation was canceled.
nvme-cli (debian, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (debian, clang, release)
The operation was canceled.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (debian, gcc, release)
The operation was canceled.
nvme-cli (fedora, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (fedora, gcc, release)
The operation was canceled.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (tumbleweed, clang, release)
The operation was canceled.
nvme-cli (tumbleweed, clang, debug)
The strategy configuration was canceled because "nvme-cli.fedora_gcc_debug" failed
nvme-cli (tumbleweed, clang, debug)
The operation was canceled.
libnvme (debian, gcc, release)
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
18.7 KB
sha256:e2a9de0a99aac1bc2dad0049c8255de0593bfd2543e79c1f14c545b0fbc42da7
log files
11.4 KB
sha256:4c18d1791ccacb495dbdb6fdf9b01d76ce087cfc0a9cacbb01f9ba87e500bbbe
logs files
16.5 KB
sha256:d0d675015a6153a6a302ae9c354c8782a914b5d143a4eea7c8ba5c33ecd250cf