Skip to content

Add Windows support to meson build system #4092

Add Windows support to meson build system

Add Windows support to meson build system #4092

Triggered via pull request March 23, 2026 22:44
Status Failure
Total duration 45s
Artifacts 3

build.yml

on: pull_request
fallback shared libraries
0s
fallback shared libraries
muon minimal static
34s
muon minimal static
make static
24s
make static
musl libc build on Debian
36s
musl libc build on Debian
musl libc minimal static build on Debian
29s
musl libc minimal static build on Debian
musl libc build on Alpine
42s
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

30 errors
nvme-cli (fedora, clang, debug)
Process completed with exit code 1.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
build libnvme and nvme-cli separately
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 (fedora, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (fedora, gcc, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" 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.
make static
Process completed with exit code 2.
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.fedora_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.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.fedora_clang_debug" failed
nvme-cli (tumbleweed, clang, release)
Value cannot be null. (Parameter 'network')
nvme-cli (tumbleweed, clang, release)
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, debug)
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.
cross (armhf)
Process completed with exit code 1.
libnvme (debian, gcc, release)
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.

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
5.61 KB
sha256:96452bd2930a07dd853b5cf17e5ecd9ae82765615e42ecd0268d386e53e2d108
log files
4.43 KB
sha256:0f05cc207fa3911cd1852e560ec6e9bcd54ef7359a090ab69433b5022b4e790c
logs files
5.81 KB
sha256:8a8a63ce31725513fcca2d9b2d5eec32ce03aa92f1e3e636d664874ca2ee1ee1