Skip to content

ci(e2e): build/run MCP server separately, and print logs on failure #154

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

Merged
merged 3 commits into from
Jun 2, 2025

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Jun 2, 2025

Before this it was hard to tell what was going wrong when the e2e tests failed because the MCP server logs are piped to a file which is never printed.

This commit builds the MCP server before running it with nohup, then prints the logs if the tests fail.

@sd2k sd2k requested a review from a team as a code owner June 2, 2025 07:33

This comment has been minimized.

Copy link
Contributor

@ioanarm ioanarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

��️

sd2k added 3 commits June 2, 2025 09:34
Before this it was hard to tell what was going wrong when the e2e tests failed because the MCP server logs are piped to a file which is never printed.

This commit builds the MCP server before running it with nohup, then prints the logs if the tests fail.
This should give us better caching for faster builds.
@sd2k sd2k force-pushed the e2e-test-logs branch from f0624b2 to b7689df Compare June 2, 2025 08:34
@sd2k sd2k merged commit d659dcb into main Jun 2, 2025
10 checks passed
@sd2k sd2k deleted the e2e-test-logs branch June 2, 2025 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants