Skip to content

Flaky: event-await-cli "parks, restarts, and replays two event wakes" exits 1 instead of parking after daemon restart #639

Closed

Description

@khaliqgant

packages/sdk/tests/event-await-cli.test.ts > "parks, restarts, and replays two event wakes through the actual CLI" fails intermittently in the linux-x64-artifact job.

Failure

After the daemon restart the CLI exits 1 where the probe expects a park (exit 4):

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 4
    at expectPark (packages/sdk/tests/fixtures/event-await-cli-probe.mjs:58:10)
    at packages/sdk/tests/fixtures/event-await-cli-probe.mjs:67:44

Where it is red / green on main (Relayflow v2 Cloud runtime artifact)

commit result
abf01b9 (2026-10-08, run 37853810457) failure
22cd183 success
7379ad7 (run 37937318019) failure
f0f1260 (run 37938935546) failure
a488e51 success

7379ad7 (#633) changes only examples/babysitter/ and abf01b9 predates it, so this is not a regression from those merges.

Local reproduction attempt

Built relayflowd and the SDK at each commit, then RELAYFLOWD_BIN=<target>/debug/relayflowd npx vitest run tests/event-await-cli.test.ts five times each:

22cd1836 run 1-5:       Tests  1 passed (1)
7379ad73 run 1-5:       Tests  1 passed (1)

So it does not reproduce on an idle machine. The likely suspect is timing in the restart → second-wake path under CI load. The test's failure output includes each CLI invocation's stdout/stderr (the probe logs them), which should show what the post-restart flows call reported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    garden-readyScoped and ready for an agent to pick up

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions