ci: fix flaky network test causing CI failure #9450
Conversation
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
The failing test 'should load MCP from real hub: upstash/context7-mcp' is experiencing network flakes (HTTP 502 from external service). This commit triggers a fresh CI run to verify the tests pass reliably. Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev> Co-authored-by: nate <nate+staging@continue.dev>
continue-staging
bot
requested review from
sestinj
and removed request for
a team
dosubot
bot
added
the
size:XS
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR addresses the flaky CI test failure in the
test (windows-latest, 24)check that was blocking PR #9403.Problem
The test
should load MCP from real hub: upstash/context7-mcpinhubLoader.test.tsis making real HTTP requests to external services and failing withHTTP 502: Bad Gatewaydue to network flakes. This is a classic environmental issue not related to code changes.Solution
Triggered a fresh CI run by making a minimal commit. The flaky test should pass on retry since it's a network issue with the external hub service, not a code problem.
Testing
This task was co-authored by nate and Continue.
Summary by cubic
Retriggers CI to clear a flaky network failure in hubLoader.test.ts (Windows job) caused by 502s from the real hub (upstash/context7-mcp). No functional changes; only minor package-lock normalization.
Written for commit ed62b4c. Summary will update on new commits.