Skip to content

[rush-daemon] Stabilize delayed-reply wire test - #6153

Open
Sean Larkin (TheLarkInn) wants to merge 1 commit into
mainfrom
thelarkinn-fix-daemon-wire-drain-flake
Open

Sean Larkin (TheLarkInn) wants to merge 1 commit into
mainfrom
thelarkinn-fix-daemon-wire-drain-flake

Conversation

@TheLarkInn

Copy link
Copy Markdown
Member

Summary

Fix the timing-sensitive daemon wire test that failed in PR #6096's Node 26 Linux job.

The old test checked a 100 ms activity window after receiving and decoding a large pong. A descheduled client could legitimately miss that window. This replaces socket-buffer assumptions and the real-time sleep with a controlled pong-write gate, explicit server activity barriers, and a controlled monotonic clock. The real socket/handshake and idle/active assertions remain; another assertion verifies that completed-write activity expires too.

No production behavior, retries, timeouts, or test enablement changes.

How it was tested

  • Reproduced the original CI assertion (Expected: true; Received: false) with a 150 ms client pause after decoding a pong.
  • Final commit: affected 8-test suite passed 25/25 runs; the same delayed-client stress passed 25/25 runs.
  • All 30 related wire/tracker tests passed; daemon dependency-closure build, Prettier, normal pre-commit hook, and Rush change verification passed.
  • Local runtime: Node 22.23.3. Node 26.7.0 acquisition required unavailable approval, so Node 26 validation remains for CI.

Control pong write completion and the tracker clock instead of relying on socket buffer sizes and a 100 ms wall-clock activity window. Preserve idle and resumed-activity assertions and verify the reply also ages out again.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 2fdae5a5-bbb9-4f39-a3e0-c0d21203e97a
Assistant-model: GPT-6.1 Sol

This branch has not been deployed

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

Labels

None yet

Projects

Status: Needs triage

Development

Successfully merging this pull request may close these issues.

2 participants