Skip to content

spec(1.18) Hardening — t/068+t/069 waldump_range retry-on-boundary-flake #121

spec(1.18) Hardening — t/068+t/069 waldump_range retry-on-boundary-flake

spec(1.18) Hardening — t/068+t/069 waldump_range retry-on-boundary-flake #121

Triggered via push May 8, 2026 10:15
Status Success
Total duration 15m 50s
Artifacts 3

ci.yml

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

Annotations

11 warnings
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/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 (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/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 (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
perf-baseline-macos-latest Expired
41 MB
sha256:cc94dede9e8867d3c151c0ba27ed0ef9b15db7dd822c52b27bc2b6b8bced21b7
perf-baseline-ubuntu-latest Expired
34.1 MB
sha256:48fc11de9cb3fee6cb0badad8810e7c8ece6885902bb61f54c44d880f5b7f916
static-analysis-report Expired
9.35 KB
sha256:98bff02ab1f310754e06c80b2de4882a5a3ea5ec706a78adb3b557114845ed69