Skip to content

Add Windows support to meson build system #4091

Add Windows support to meson build system

Add Windows support to meson build system #4091

Triggered via pull request March 23, 2026 22:41
Status Failure
Total duration 5m 25s
Artifacts 3

build.yml

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

Annotations

37 errors
musl libc build on Alpine
Process completed with exit code 1.
musl libc minimal static build on Debian
Process completed with exit code 1.
muon minimal static
Process completed with exit code 1.
musl libc build on Debian
Process completed with exit code 1.
build libnvme and nvme-cli separately
Process completed with exit code 1.
libnvme (debian, gcc, release)
Process completed with exit code 1.
nvme-cli (debian, clang, debug)
Process completed with exit code 1.
nvme-cli (debian, clang, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
nvme-cli (fedora, clang, release)
The strategy configuration was canceled because "nvme-cli.debian_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 (fedora, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
cross (s390x)
Process completed with exit code 1.
nvme-cli (debian, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_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, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
nvme-cli (tumbleweed, clang, debug)
A task was canceled.
cross (ppc64le)
The strategy configuration was canceled because "cross.s390x" 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 (fedora, clang, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
nvme-cli (fedora, clang, debug)
The operation was canceled.
nvme-cli (fedora, clang, debug)
Process completed with exit code 1.
nvme-cli (debian, gcc, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
nvme-cli (debian, gcc, release)
Value cannot be null. (Parameter 'network')
nvme-cli (debian, gcc, release)
The operation was canceled.
nvme-cli (tumbleweed, gcc, release)
The strategy configuration was canceled because "nvme-cli.debian_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.debian_clang_debug" failed
nvme-cli (fedora, gcc, release)
The operation was canceled.
nvme-cli (tumbleweed, gcc, debug)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed
nvme-cli (tumbleweed, gcc, debug)
The operation was canceled.
cross (armhf)
The strategy configuration was canceled because "cross.s390x" failed
cross (armhf)
The operation was canceled.
make static
Process completed with exit code 2.
nvme-cli (tumbleweed, clang, release)
The strategy configuration was canceled because "nvme-cli.debian_clang_debug" failed

Artifacts

Produced during runtime
Name Size Digest
libnvme logs files
4.05 KB
sha256:b5d0a46d887f2c691bf2b720309f81dbc4d47a54e05d08a7434e7c11d843906e
log files
3.02 KB
sha256:1d175c265f661a6600f09cec239d308aff49270ec7a5eee0924260663df44deb
logs files
4.11 KB
sha256:486f09fd81e517e31616efb671388ab6fdf253bca02411d5b62c3a0542e53ca8