Skip to content

Repository mismatch: Unable to fix StdioClientTransportTests - files not found#124444

Closed
Copilot wants to merge 1 commit intomainfrom
copilot/fix-stdio-client-transport-test
Closed

Repository mismatch: Unable to fix StdioClientTransportTests - files not found#124444
Copilot wants to merge 1 commit intomainfrom
copilot/fix-stdio-client-transport-test

Conversation

Copy link
Contributor

Copilot AI commented Feb 15, 2026

Description

Cannot proceed with fixing the failing StdioClientTransportTests.CreateAsync_ValidProcessInvalidServer_StdErrCallbackInvoked test because the referenced files do not exist in this repository.

Problem

The problem statement references files from modelcontextprotocol/csharp-sdk:

  • src/ModelContextProtocol.Tests/Transport/StdioClientTransportTests.cs
  • src/ModelContextProtocol.Core/McpSessionHandler.cs

However, the current repository is dotnet/runtime, which does not contain any ModelContextProtocol-related code.

Changes Made

None. No changes can be made without access to the correct repository or clarification on the task requirements.

Next Steps

Requires clarification:

  • Clone the correct repository (modelcontextprotocol/csharp-sdk), OR
  • Provide different task requirements for dotnet/runtime
Original prompt

Investigate and fix the issue for the failing job in https://github.com/modelcontextprotocol/csharp-sdk/actions/runs/22038164601/job/63674819004?pr=1279.

Summary of the failure:

  • Test: ModelContextProtocol.Tests.Transport.StdioClientTransportTests.CreateAsync_ValidProcessInvalidServer_StdErrCallbackInvoked is failing.
  • Error: System.IO.IOException: The server shut down unexpectedly. at McpSessionHandler.SendRequestAsync(...)
  • Context: This usually occurs when the test server process exits prematurely and the client attempts a request. In integration-style tests, ensure the server stub/process is valid and stays alive for the required test duration, or that the test expects and asserts on this failure mode.

Actions:

  1. Review the test (StdioClientTransportTests.cs). If it is designed to trigger server shutdown, update it to assert for IOException instead of failing.
  2. If the process should not terminate, review the server stub/executable path, process invocation and lifetime in the test setup.
  3. Update the code/test to correctly represent and assert the expected behavior (either pass if IOException as expected, or fix the process if unintentional).
  4. Add/modify test code to ensure robust error handling for server unavailability scenarios.
  5. Verify the fix across all supported platforms as the workflow matrix includes multiple OSes (Linux/macOS/Windows).

Provide code suggestions, if fixes are required in src/ModelContextProtocol.Tests/Transport/StdioClientTransportTests.cs, so that tests do not fail on expected server shutdown behavior and robustly handle server startup/termination edge cases.

References:

Make the integration tests robust with correct exception handling for server shutdown scenarios.

This pull request was created from Copilot chat.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Investigate and fix failing job for StdioClientTransportTests Repository mismatch: Unable to fix StdioClientTransportTests - files not found Feb 15, 2026
Copilot AI requested a review from stephentoub February 15, 2026 16:58
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Feb 15, 2026
@stephentoub stephentoub deleted the copilot/fix-stdio-client-transport-test branch February 15, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants