Skip to content

Probe: Windows state-write stall (do not merge) - #22

Closed
maxrossignol wants to merge 1 commit into
mainfrom
probe/windows-state-writes
Closed

maxrossignol wants to merge 1 commit into
mainfrom
probe/windows-state-writes

Conversation

@maxrossignol

Copy link
Copy Markdown
Contributor

Throwaway diagnosis for main's Windows failure after #21: server::tests::concurrent_state_writes_all_succeed_and_the_last_one_is_current timed out after 60 s (run 39420674701), where the whole unit binary normally takes 3 to 16 s on Windows.

This branch times each phase of write_private_atomic (open, write, sync_all, rename, ACL) and each writer's round, prints Defender's state, then runs the test alone 30 times and the full unit suite 10 times on windows-latest only. It is closed unmerged once the cause is known.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@maxrossignol

Copy link
Copy Markdown
Contributor Author

Findings: 30 isolated runs and 10 full unit-suite runs on windows-latest all passed; 150 writes took 1.1–4.2 s, no write phase (open, write, sync_all, rename, ACL) ever exceeded 250 ms, and Defender real-time protection is off on the runners. With one lock order on every write path (state_write first) and no writer panic, the 60 s timeout on main (run 39420674701) was a stall of that runner (its build was also ~50% slower than usual), not a code defect. Closing unmerged.

@maxrossignol
maxrossignol deleted the probe/windows-state-writes branch October 20, 2026 12:57
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