Skip to content
CI

fix: batch accumulator doesn't flush when source iter raises #75

Sign in to view logs

fix: batch accumulator doesn't flush when source iter raises

fix: batch accumulator doesn't flush when source iter raises #75

Triggered via pull request May 11, 2026 21:31
@quettabitquettabit
opened #49
qb/iss-43
Status Success
Total duration 6m 38s
Artifacts 1

ci.yml

on: pull_request
Build s2-lite  /  Build s2-lite
5m 43s
Build s2-lite / Build s2-lite
Local Checks (code quality, unit tests, docs build)
22s
Local Checks (code quality, unit tests, docs build)
s2-cloud integration tests
1m 41s
s2-cloud integration tests
Matrix: s2-lite integration tests / test
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
s2-cloud integration tests
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-b34df8ee98555dd219633c8a4f1dfe18ad3dd687e39b84235b1bda5c2524d5b1, another job may be creating this cache.
Build s2-lite / Build s2-lite
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-protoc@c65c819552d16ad3c9b72d9dfd5ba5237b9c906b. 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
server-binary Expired
9.39 MB
sha256:e22b752bc8cce8ca31865eeb58d9705c3032d31f60ab1efc989fbd7c7d669bcd