Skip to content

Fixes for DH-HMAC-CHAP #4041

Fixes for DH-HMAC-CHAP

Fixes for DH-HMAC-CHAP #4041

Triggered via pull request March 17, 2026 11:55
Status Failure
Total duration 42s
Artifacts 3

build.yml

on: pull_request
fallback shared libraries
0s
fallback shared libraries
muon minimal static
27s
muon minimal static
make static
29s
make static
musl libc build on Debian
24s
musl libc build on Debian
musl libc minimal static build on Debian
20s
musl libc minimal static build on Debian
musl libc build on Alpine
36s
musl libc build on Alpine
build libnvme and nvme-cli separately
22s
build libnvme and nvme-cli separately
Matrix: cross
Matrix: libnvme
Matrix: nvme-cli
Fit to window
Zoom out
Zoom in

Annotations

34 errors
musl libc minimal static build on Debian
Process completed with exit code 1.
nvme-cli (tumbleweed, 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 (tumbleweed, clang, debug)
Process completed with exit code 1.
nvme-cli (tumbleweed, gcc, release)
Process completed with exit code 1.
nvme-cli (fedora, gcc, release)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (fedora, gcc, debug)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (fedora, clang, debug)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.tumbleweed_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.
build libnvme and nvme-cli separately
Process completed with exit code 1.
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (debian, 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 (debian, gcc, debug)
Process completed with exit code 1.
musl libc build on Debian
Process completed with exit code 1.
nvme-cli (debian, clang, release)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (debian, clang, release)
The operation was canceled.
nvme-cli (debian, clang, debug)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (debian, clang, debug)
The operation was canceled.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (debian, gcc, release)
The operation was canceled.
muon minimal static
Process completed with exit code 1.
make static
Process completed with exit code 2.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.tumbleweed_clang_debug" failed
nvme-cli (tumbleweed, clang, release)
The operation was canceled.
libnvme (debian, gcc, release)
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.
musl libc build on Alpine
Process completed with exit code 1.
cross (ppc64le)
The strategy configuration was canceled because "cross.armhf" failed
cross (ppc64le)
The operation was canceled.

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
5.62 KB
sha256:2fc85669ef12ca12af705cb8669e129d960523983a810cbe915cdee571022a8f
log files
4.52 KB
sha256:87a875bf044908fd87bde15bf4d904f5da4bf00089a05a59503ffadd2f576e29
logs files
8.66 KB
sha256:743872fbdac1bf41209739488706338402d955e5c4a6a51716882cdfcac762f6