-
Notifications
You must be signed in to change notification settings - Fork 46
Fix test expectations for MCP gateway config piping format #9851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
|
🎉 Yo ho ho! Changeset Generator found the treasure and completed successfully! ⚓💰 |
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
Smoke Test ResultsLast 2 Merged PRs:
Test Results:
Overall Status: PARTIAL PASS (4/5 tests passed) cc @pelikhan
|
Smoke Test Results - Claude EngineLast 2 merged PRs:
Test Results:
Status: FAIL (Serena Go test failed - no basic Go command execution available)
|
Recent MCP gateway changes (PR #9839) modified how MCP configurations are passed to the gateway script - from writing to files to piping directly. Three test cases in
engine_helpers_shared_test.gostill expected the old format.Changes
TestRenderJSONMCPConfig:cat > /tmp/test-config.json << EOFtocat << MCPCONFIG_EOF | bash /opt/gh-aw/actions/start_mcp_gateway.shEOFtoMCPCONFIG_EOFVerification
TestRenderJSONMCPConfigsubtests pass--validateworks correctlyNote
Other engine-specific tests (Codex, Copilot, Custom) still fail - these were already broken by PR #9839 and expect the old format without the MCP gateway JSON section. Out of scope for this fix.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.