Skip to content

Uniformed server side stdout prints and parseCLI #2609

Uniformed server side stdout prints and parseCLI

Uniformed server side stdout prints and parseCLI #2609

Triggered via pull request April 27, 2026 14:49
Status Failure
Total duration 2m 5s
Artifacts 2

ci-tests.yaml

on: pull_request
Matrix: format-check
Matrix: unit-tests
Check codespell conformance
9s
Check codespell conformance
Matrix: Check Docker image
Codecov report upload
Codecov report upload
Fit to window
Zoom out
Zoom in

Annotations

55 errors and 2 warnings
Check capio/tests clang-format conformance
The strategy configuration was canceled because "format-check.capio_server" failed
Check capio/posix clang-format conformance
The strategy configuration was canceled because "format-check.capio_server" failed
Check capio/common clang-format conformance
The strategy configuration was canceled because "format-check.capio_server" failed
Build Debug with gcc:11
Process completed with exit code 1.
Build Debug with gcc:9
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with gcc:12
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:15.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:17.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:14.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with gcc:15
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:20.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:9
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with gcc:13
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:21.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:12
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:15.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:18-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:16.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:17.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:17.0-trixie
The operation was canceled.
Build Debug with gcc:10
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with gcc:10
Process completed with exit code 1.
Build Debug with gcc:14
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with gcc:14
Process completed with exit code 1.
Build Release with gcc:11
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:11
Process completed with exit code 1.
Build Release with gcc:13
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:13
Process completed with exit code 1.
Check Docker image (Debug)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c mkdir -p /opt/capio/build && cmake -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} -DCAPIO_BUILD_TESTS=${CAPIO_BUILD_TESTS} -DCAPIO_LOG=${CAPIO_LOG} -G Ninja -B /opt/capio/build -S /opt/capio && cmake --build /opt/capio/build -j$(nproc) && cmake --install /opt/capio/build --prefix /usr/local" did not complete successfully: exit code: 1
Check Docker image (Release)
The strategy configuration was canceled because "docker-check.Debug" failed
Check Docker image (Release)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c mkdir -p /opt/capio/build && cmake -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} -DCAPIO_BUILD_TESTS=${CAPIO_BUILD_TESTS} -DCAPIO_LOG=${CAPIO_LOG} -G Ninja -B /opt/capio/build -S /opt/capio && cmake --build /opt/capio/build -j$(nproc) && cmake --install /opt/capio/build --prefix /usr/local" did not complete successfully: exit code: 1
Build Release with gcc:10
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:10
Process completed with exit code 1.
Build Release with zhongruoyu/llvm-ports:19.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:19.1-bullseye
The operation was canceled.
Build Release with zhongruoyu/llvm-ports:13.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:13.0-trixie
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:16.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:16.0-trixie
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:19.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:19.1-bullseye
The operation was canceled.
Build Release with zhongruoyu/llvm-ports:14.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:14.0-trixie
The operation was canceled.
Build Release with gcc:15
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:15
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:21.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:21.1-bullseye
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:13.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:13.0-trixie
The operation was canceled.
Build Release with gcc:14
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with gcc:14
Process completed with exit code 1.
Build Debug with zhongruoyu/llvm-ports:18-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Debug with zhongruoyu/llvm-ports:18-trixie
The operation was canceled.
Build Release with zhongruoyu/llvm-ports:20.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_11" failed
Build Release with zhongruoyu/llvm-ports:20.1-bullseye
The operation was canceled.
Check Docker image (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check Docker image (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
High-Performance-IO~capio~49GVU6.dockerbuild
51.1 KB
sha256:3512b8950f57daea4bdcfde353064175ec9e2509b83cd410d038e315ef7ad81d
High-Performance-IO~capio~CW2655.dockerbuild
52 KB
sha256:bef938473e1bf8088c0b5471d61b14faf4372e900957bcd099de67a8640275ee