Latest Results
core/storage: add red-first coverage for the saveAllCursors port
Two layers covering the runtime added in #7341:
- Internals (storage::btree::tests::save_all_cursors, 8 cases) pin
the individual primitives — peer registration, has_peers toggling,
try_save_position_for_external_balance's Saved/MustInvalidate
outcomes, restore_context's CURSOR_SKIPNEXT semantics, and
clear_btree's auto-invalidation of peers. 4 of the 8 go red when
drive_pending_peer_save and invalidate_peer_cursors are stubbed
out; the remaining 4 cover the registry API surface that is exercised
even on the fast path.
- SQL surface (testing/sqltests/tests/save-all-cursors.sqltest, 4
cases) extends the window-selfjoin-reset-sorter pattern: a window
function over a triple self-joined source forces ephemeral
overflow + ResetSorter, leaving OpenDup peer cursors that need
the registry's auto-invalidate. Variants cover multi-partition
data, DELETE driven by a scalar subquery, UPDATE driven by an IN
subquery, and a materialized-CTE source. All four fail with
"parent page 2 is a leaf page, expected interior page" when the
runtime is reverted. Latest Branches
0%
0%
0%
© 2026 CodSpeed Technology