Intermittent: memory_usage_zset test gets ConnectionReset (possible server panic in MEMORY USAGE of a sorted set) · Issue #506 · kividbio/kividb · GitHub
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
Intermittent: memory_usage_zset test gets ConnectionReset (possible server panic in MEMORY USAGE of a sorted set) #506
tests/memory_usage_zset.rsmemory_usage_of_sorted_sets_is_what_their_keys_take failed once in CI on #503 (run 42305394446, rust job). The failure was ConnectionReset at tests/memory_usage/mod.rs:229, meaning the server dropped the connection mid-test. It passed on #468's CI on the same master, so it's intermittent.
A connection reset usually means the command panicked. Start by checking the server log of a failing run. Likely candidates are the new sorted-set accounting from #492 (the per-member allocation check, Arc::strong_count rescore heuristic) and #490's key changes, under concurrent writes. Reproduce by looping the test on a VM.
Activity