Skip to content

[rush-client-core] Allow slow daemon startup in queued resend tests - #6160

Open
Sean Larkin (TheLarkInn) wants to merge 2 commits into
microsoft:mainfrom
TheLarkInn:user/selarkin/bot-rush-client-publish-timeout
Open

Sean Larkin (TheLarkInn) wants to merge 2 commits into
microsoft:mainfrom
TheLarkInn:user/selarkin/bot-rush-client-publish-timeout

Conversation

@TheLarkInn

Copy link
Copy Markdown
Member

Summary

Fix the Jest timeout blocking RushStack NPM Publish 12838.

Give the queued-request resend integration suite a 30-second default, matching the existing real-process test pattern. It starts and replaces real daemon processes; its 7-second per-start allowance already exceeds Jest's 5-second default. Existing assertions, explicit per-test timeouts and production behavior are unchanged.

How it was tested

  • Reproduced the exact failing test and 5,000 ms timeout by applying the fixture's existing 2,700 ms startup delay to both daemon starts.
  • With this change, the identical delayed-start test passed (8.857-second suite); the delay probe is not part of the patch.
  • All 12 queued-request resend tests passed with FORCE_COLOR=1 on Linux / Node 22.23.3.
  • Affected package and dependency-closure build, including type checking and lint, passed. Rush change verification passed.

Required CI and human review remain required; no pipeline or policy retries were requested.

Give the real-process queued-request resend suite a 30-second default instead of Jest�4s 5 seconds. This fixes the timeout in RushStack NPM Publish 12838 without changing runtime deadlines, assertions, or explicit per-test bounds.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 196de551-3c6b-4904-ba03-e5c830ee0dbe
Add the required no-release change description for the queued-request resend integration test fix.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 196de551-3c6b-4904-ba03-e5c830ee0dbe

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