You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Test: make cooperative nursery retry assertion scheduler-stable #509
context.test.parallel_js: multi-age cooperative nursery retains old-owner graph asserts that gc_cooperative_timeouts is exactly zero. The cooperative collector intentionally uses a bounded 100 ms rendezvous and retries after a peer misses that deadline. Under a 10-shard Debug unit run this assertion failed twice (expected 0, found 2) while the graph, collection, parking, promotion, cleanup, and denominator invariants all completed.
A nearby moving-nursery test already documents the scheduler-stable contract: every elected attempt has exactly one terminal outcome, so attempts == collections + timeouts; the retry count depends on host scheduling.
The fix preserves successful collections, tenuring, peer parks, promotion, graph integrity, and clean conductor state, while accounting for the collector's documented bounded rendezvous retries (attempts == collections + timeouts). The adjacent caller-scope witness now uses the same scheduler-stable contract.
Activity
chrisbbreuer commentedon Aug 9, 2026
Implemented and landed on
mainas test(gc): stabilize sharded concurrency coverage.The fix preserves successful collections, tenuring, peer parks, promotion, graph integrity, and clean conductor state, while accounting for the collector's documented bounded rendezvous retries (
attempts == collections + timeouts). The adjacent caller-scope witness now uses the same scheduler-stable contract.Validation:
Closed by 5624fcf. Refs #494 and #476.