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
memory: two Streamable HTTP tests time out intermittently on Windows CI #5570
__tests__/http.test.ts:68: "serves a … client and keeps the graph across its requests" (one of the it.each(ERAS) cases): Test timed out in 5000ms.
__tests__/write-limits.test.ts:304: "write limits over Streamable HTTP > holds the endpoint's write tools to the limits it was given": Test timed out in 5000ms.
The same leg passed on the two preceding v2/main commits (b9a69dcb, 88af1edb), and nothing merged between them and aef8fd72 touches src/memory. Both failures are in the two files that start a real HTTP endpoint; every other memory test in the run passed, and the run's total test time was 34 s.
Why it matters
AGENTS.md forbids retries because a retry reports a test that sometimes fails as passing; a rerun of the job does the same thing by hand. The cause should be found rather than rerun around.
Whether the two tests are slow on Windows in every run (close to the 5 s default) or only occasionally. The per-test durations in the passing attempt of the run above will say.
Done when
The cause is identified and fixed, or, if the tests are legitimately slow on Windows, they carry an explicit timeout with a comment giving the measured duration. No retry.
Test memory (Windows) passes repeatedly on the fix's PR.
Activity
chore(memory): TEMPORARY per-test durations for the Windows diagnostic (
fix(memory): give the real-endpoint HTTP tests a timeout clear of a s…