test(runtime): io cancelled-wait leak check fails tier B at random #338
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
test_io_a_cancelled_wait_releases_its_registration(runtimeC tests,io_test.c:301) fails intermittently with "2 blocks leaked".Seen 2026-10-12:
mainatd679af0(merge of #330):ci / tier B (linux-x64)andci / gatesred, only this test failing; tier B on the same tree was green in the PR run.The change under test (#330, git: sources) does not touch the runtime, so this is a timing-dependent leak check, not a regression. Likely cause: the cancelled wait's registration is released asynchronously (reactor/completion thread) and the leak count is sampled before the release lands.
Done when: the test waits for (or deterministically drives) the release before counting allocations, and 20 consecutive tier B runs show no leak report. Related: #244 (timing-dependent language-server tests).
[loop:torbscript] decided by the loop: main CI is red on
d679af0(tier B + gates) from this flake, so it comes first. Scope: make the test deterministic (wait for or drive the registration release before the leak count), one PR, no seed impact. Goal and acceptance criteria are in the body. next: implement[loop:torbscript] claim implement by session:loop-torbscript-20261012 until 2026-10-12T22:02Z