Test: one write per offer in the reconnect backfill test (CI flake) #262

Merged
cmoriarty merged 1 commit from fix/backfill-test-one-write into main 2026-10-27 18:03:51 -04:00
Owner

test_a_reconnect_backfill_adds_nothing_the_stream_already_delivered wrote each part in its own write, a round trip to the writer thread. On a loaded runner two dozen of those took 1.1 to 3.0 s against the 1 s limit:

  • CI run 231 (PR #261's first run, slow job setup)
  • CI run 233 (the push of #261's merge, while the deploy built its image)

Locally, and on Linux alone, they take 0.01 s. Now each offer is one write; the parts still go through append_oc_part in order, so the test still fails if a backfill adds a row.

🤖 Generated with Claude Code

`test_a_reconnect_backfill_adds_nothing_the_stream_already_delivered` wrote each part in its own write, a round trip to the writer thread. On a loaded runner two dozen of those took 1.1 to 3.0 s against the 1 s limit: - CI run 231 (PR #261's first run, slow job setup) - CI run 233 (the push of #261's merge, while the deploy built its image) Locally, and on Linux alone, they take 0.01 s. Now each offer is one write; the parts still go through `append_oc_part` in order, so the test still fails if a backfill adds a row. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
test(agent): one write per offer in the reconnect backfill test
All checks were successful
test / suite (pull_request) Successful in 38s
6003723460
Each part was its own write, a round trip to the writer thread. On a loaded CI runner
two dozen of them took 1.1 to 3.0 s against the 1 s limit (CI runs 231 and 233, while
the deploy built its image); they take 0.01 s on a laptop. The parts still go through
append_oc_part in order, so the test still fails if a backfill adds a row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cmoriarty deleted branch fix/backfill-test-one-write 2026-10-27 18:03:51 -04:00
Author
Owner

The test still times out on a loaded runner after this fix: #299.

The test still times out on a loaded runner after this fix: #299.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid!262
No description provided.