Skip to content

feat(1.17): walwriter BOC — atomic SCN hot path + walwriter periodic … #67

feat(1.17): walwriter BOC — atomic SCN hot path + walwriter periodic …

feat(1.17): walwriter BOC — atomic SCN hot path + walwriter periodic … #67

Triggered via push May 5, 2026 03:52
Status Failure
Total duration 7m 34s
Artifacts 1

ci.yml

on: push
Validate (comment headers + format + tidy + commit msg)
57s
Validate (comment headers + format + tidy + commit msg)
Build+Test (--disable-cluster regression)
3m 15s
Build+Test (--disable-cluster regression)
Security (cppcheck + scan-build)
1m 4s
Security (cppcheck + scan-build)
Matrix: build-test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
Security (cppcheck + scan-build)
Process completed with exit code 1.
Validate (comment headers + format + tidy + commit msg)
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. 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/
Security (cppcheck + scan-build)
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/upload-artifact@v4. 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/
Build+Test (--disable-cluster regression)
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. 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/
Build+Test (ubuntu-latest)
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. 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/
Build+Test (macos-latest)
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. 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/
Build+Test (macos-latest)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
Build+Test (macos-latest)
openssl@3 3.6.2 is already installed and up-to-date. To reinstall 3.6.2, run: brew reinstall openssl@3
Build+Test (macos-latest)
zstd 1.5.7_1 is already installed and up-to-date. To reinstall 1.5.7_1, run: brew reinstall zstd
Build+Test (macos-latest)
lz4 1.10.0 is already installed and up-to-date. To reinstall 1.10.0, run: brew reinstall lz4
Build+Test (macos-latest)
icu4c@78 78.3 is already installed and up-to-date. To reinstall 78.3, run: brew reinstall icu4c@78
Build+Test (macos-latest)
readline 8.3.3 is already installed and up-to-date. To reinstall 8.3.3, run: brew reinstall readline

Artifacts

Produced during runtime
Name Size Digest
static-analysis-report Expired
7.94 KB
sha256:3ba72d857df83ebac7e1694e0b1c759475360888e79f566d0596418e040f7c63