Skip to content

Tests(fix[control]): Restore wrapper readiness - #19

Closed
tony wants to merge 1 commit into
masterfrom
fix/control-wrapper-readiness
Closed

Tests(fix[control]): Restore wrapper readiness#19
tony wants to merge 1 commit into
masterfrom
fix/control-wrapper-readiness

Conversation

@tony

@tony tony commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Wait for executable readiness: Hold the shared wrapper publication boundary until an execution probe no longer reports ETXTBSY.
  • Keep the retry narrow: Preserve atomic publication and retry only the transient writable-inode condition before control-mode setup begins.
  • Remove redundant probes: Let the publication helper own readiness instead of repeating immediate assertions in each integration test.

Test plan

  • Reproduce the writable-descriptor ETXTBSY boundary with a controlled process probe.
  • Run the focused control-mode integration tests on .NET 8 and .NET 10.
  • Verify formatting and build the solution in Release mode with warnings treated as errors.
  • Run the package-consumer, NativeAOT, example, documentation, and supported-tmux gates.

why: Atomic rename closes the publisher's handle, but a sibling fork can
retain a writable descriptor to the inode until exec. An immediate probe
can therefore fail with ETXTBSY before production code runs.

what:
- Wait out only ETXTBSY at the shared wrapper publication boundary
- Remove redundant immediate probes from the control-mode tests
@tony tony closed this Aug 30, 2026
@tony
tony deleted the fix/control-wrapper-readiness branch August 30, 2026 22:41
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