Skip to content

libnvmf: replace nvmf_get_discovery_log() with opaque-args API #4243

libnvmf: replace nvmf_get_discovery_log() with opaque-args API

libnvmf: replace nvmf_get_discovery_log() with opaque-args API #4243

Triggered via pull request April 9, 2026 17:06
Status Failure
Total duration 1m 53s
Artifacts 3

build.yml

on: pull_request
fallback shared libraries
fallback shared libraries
muon minimal static
28s
muon minimal static
make static
24s
make static
musl libc build on Debian
20s
musl libc build on Debian
musl libc minimal static build on Debian
27s
musl libc minimal static build on Debian
musl libc build on Alpine
32s
musl libc build on Alpine
build libnvme and nvme-cli separately
22s
build libnvme and nvme-cli separately
windows-msys2-ucrt64
1m 49s
windows-msys2-ucrt64
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.
libnvme (debian, gcc, release)
Process completed with exit code 1.
nvme-cli (debian, clang, release)
Process completed with exit code 1.
nvme-cli (fedora, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
build libnvme and nvme-cli separately
Process completed with exit code 1.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (tumbleweed, gcc, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (tumbleweed, clang, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
cross (armhf)
Process completed with exit code 1.
nvme-cli (fedora, gcc, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (fedora, gcc, 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, gcc, release)
Process completed with exit code 1.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (debian, gcc, 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 (debian, gcc, release)
Process completed with exit code 1.
make static
Process completed with exit code 2.
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (tumbleweed, gcc, debug)
The operation was canceled.
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (fedora, clang, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (fedora, clang, debug)
The operation was canceled.
nvme-cli (fedora, clang, release)
The operation was canceled.
nvme-cli (debian, clang, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_release" failed
nvme-cli (debian, clang, 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 (debian, clang, debug)
Process completed with exit code 1.
musl libc build on Alpine
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)
The operation was canceled.
muon minimal static
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
5.63 KB
sha256:4cd5bd7b093968893f65bbcf797c9252a1ddf83c5cdd4a47a8eed60c8cc169df
log files
4.44 KB
sha256:8078689195e118ee8550da42065f3610a6d2e09a4a1fc02305ce253a9e05702d
logs files
6.04 KB
sha256:320ae9a0773de95a4f7e76c0c2dd806d6e38966b191cf00a3d8832736d8f0490