Skip to content

perf: hot-path fixes — ring buffers, futex waits, handleGet header #120

perf: hot-path fixes — ring buffers, futex waits, handleGet header

perf: hot-path fixes — ring buffers, futex waits, handleGet header #120

Triggered via pull request April 18, 2026 10:25
Status Failure
Total duration 1m 27s
Artifacts

ci.yml

on: pull_request
Matrix: Build & Test
Python FFI Test
Python FFI Test
Benchmark
Benchmark
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Build & Test (ubuntu-latest)
Process completed with exit code 1.
Build & Test (macos-latest)
The strategy configuration was canceled because "build.ubuntu-latest" failed
Build & Test (macos-latest)
The operation was canceled.
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, mlugg/setup-zig@v2. 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, mlugg/setup-zig@v2. 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/