Skip to content

DIAGNOSTIC: Windows hook spawn timing (do not merge) - #2

Closed
packetloss404 wants to merge 5 commits into
mainfrom
diag/windows-hook-timing
Closed

DIAGNOSTIC: Windows hook spawn timing (do not merge)#2
packetloss404 wants to merge 5 commits into
mainfrom
diag/windows-hook-timing

Conversation

@packetloss404

Copy link
Copy Markdown
Owner

Temporary instrumentation to confirm the diagnosis for the flaky
TestRunUserPromptSubmit_CollectsStdout on test (windows-latest).

Not for merge. Will be closed once the numbers are collected.

🤖 Generated with Claude Code

packetloss404 and others added 5 commits September 5, 2026 10:47
Temporary instrumentation, not for merge. Gives every Windows hook test a
120s budget so the runner reports what the hook actually costs instead of
truncating it at the budget, and adds a tiered measurement that separates
bare CreateProcess from PowerShell startup from stdin plumbing from the
internal/hooks wrapper.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
go test discards a passing package's stderr, which hid the numbers on
exactly the runs that succeeded. Record to a file instead, and probe a
bare CreateProcess and a cold PowerShell immediately before the first
hook so machine contention can be told apart from interpreter start-up.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@packetloss404

Copy link
Copy Markdown
Owner Author

Diagnosis confirmed; closing the instrumentation. The measurements it produced are in the fix at #3.

First powershell -Command "exit 0" per job on four windows-latest runners: 4.625s, 4.867s, 4.328s, 4.660s. Every later one: 0.16-0.19s. Bare cmd.exe CreateProcess at the same instant: 15-38ms.

The branch diag/windows-hook-timing is left in place in case the instrumentation is wanted again; it is not for merge.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant