Skip to content

memory: two Streamable HTTP tests time out intermittently on Windows CI #5570

Open

Description

@cliffhall

Problem

Two of memory's Streamable HTTP tests timed out on the Windows CI leg and passed on a rerun of the same commit, so they are flaky.

  • Run: https://github.com/modelcontextprotocol/servers/actions/runs/44246763473 (attempt 1 failed, attempt 2 passed), v2/main at aef8fd72, job Test memory (Windows).
  • __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.

What to find out

  • Whether the time goes to starting the endpoint, to the client's connect and era negotiation, or to lock acquisition on the graph file (the stale-lock path changed in fix(memory): never delete a successor's live lock when breaking a stale one #5563; it passed Windows CI there, but rule it in or out).
  • 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.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingserver-memoryReference implementation for the Memory MCP server - src/memoryv2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions