Skip to content

Privatize CapioFile public class attributes #2447

Privatize CapioFile public class attributes

Privatize CapioFile public class attributes #2447

Re-run triggered March 12, 2026 08:58
Status Cancelled
Total duration 29m 27s
Artifacts

ci-tests.yaml

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

Annotations

53 errors and 20 warnings
Build Debug with gcc:9
The action 'Run tests' has timed out after 5 minutes.
Build Debug with gcc:11
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:20.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with gcc:14
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:16.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:21.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:17.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:13.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:11
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:16.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:14.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:12
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:21.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:20.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with gcc:10
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:20.1-bullseye
The operation was canceled.
Build Debug with gcc:10
The operation was canceled.
Build Debug with gcc:13
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with gcc:13
The operation was canceled.
Build Release with zhongruoyu/llvm-ports:18-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:18-trixie
The operation was canceled.
Build Debug with gcc:15
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with gcc:15
The operation was canceled.
Build Debug with gcc:12
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with gcc:12
The operation was canceled.
Build Release with gcc:15
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:15
The operation was canceled.
Build Release with gcc:13
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:13
The operation was canceled.
Build Release with gcc:9
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:9
The operation was canceled.
Build Release with gcc:10
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:10
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:14.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:14.0-trixie
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:18-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:18-trixie
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:15.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug with zhongruoyu/llvm-ports:15.0-trixie
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:17.0-trixie
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:14
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with gcc:14
The operation was canceled.
Build Debug with zhongruoyu/llvm-ports:19.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Debug 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_9" failed
Build Release with zhongruoyu/llvm-ports:13.0-trixie
The operation was canceled.
Build Release with zhongruoyu/llvm-ports:19.1-bullseye
The strategy configuration was canceled because "unit-tests.Debug_gcc_9" failed
Build Release with zhongruoyu/llvm-ports:19.1-bullseye
The operation was canceled.
Check Docker image (Debug)
Canceling since a higher priority waiting request for build-213 exists
Check Docker image (Debug)
The operation was canceled.
Check Docker image (Release)
Canceling since a higher priority waiting request for build-213 exists
Check Docker image (Release)
The operation was canceled.
CI Tests
Canceling since a higher priority waiting request for build-213 exists
Build Debug with gcc:9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with zhongruoyu/llvm-ports:20.1-bullseye
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with gcc:10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with gcc:13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with zhongruoyu/llvm-ports:18-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with gcc:15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with gcc:12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with gcc:15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with gcc:13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with gcc:9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with gcc:10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with zhongruoyu/llvm-ports:14.0-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with zhongruoyu/llvm-ports:18-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with zhongruoyu/llvm-ports:15.0-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with gcc:14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Debug with zhongruoyu/llvm-ports:19.1-bullseye
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with zhongruoyu/llvm-ports:13.0-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build Release with zhongruoyu/llvm-ports:19.1-bullseye
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/checkout@v4, docker/build-push-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/