Repository navigation
Isolate MCP executable validation from executor saturation - #8
Merged
Merged
Conversation
Run the real MCP executable tests as a serialized suite in a separate required validation phase, keeping concurrent session admission inside its test. The default concurrent suite includes synchronous executor saturation and compiler fixtures, which can starve HTTP callbacks past their existing deadlines. Include the executable suite in staged and unpacked release acceptance. Capture HTTP server output in files, require the configured server to answer before connecting, and read buffered socket headers before checking a pending receive deadline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default concurrent run mixes real HTTP clients with synchronous executor saturation and compiler fixtures. In the failed run, all four host cases timed out and the socket readers resumed after their deadline while many otherwise immediate tests took about 28 seconds.
Move executable MCP coverage into a serialized suite and require a separate CI validation phase. The four concurrent initialization requests still run together and verify capacity release. Staged and unpacked release validation include the new suite. HTTP startup checks require the configured server response, server output is captured without pipe backpressure, and buffered response headers are read before a pending receive deadline is checked. Existing timeouts are unchanged.
Validation: 33 release-tool tests passed, public-content validation passed, Swift syntax parsing passed, and git diff --check passed. Swift integration and packaging validation run in CI. No release is requested.