[Bugfix #725] Fix CI: move bridge-mode test to integration suite#726
Merged
waleedkadous merged 2 commits intocluesmith:mainfrom May 7, 2026
Merged
[Bugfix #725] Fix CI: move bridge-mode test to integration suite#726waleedkadous merged 2 commits intocluesmith:mainfrom
waleedkadous merged 2 commits intocluesmith:mainfrom
Conversation
bridge-mode.test.ts spawns Tower from dist/ which doesn't exist in the unit-test CI job. Renaming to .e2e.test.ts excludes it from the default vitest config (which excludes **/*.e2e.test.ts) and includes it in vitest.e2e.config.ts (which includes src/**/*.e2e.test.ts), matching the existing convention for server-spawning integration tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
Architect ReviewLow-risk CI fix. The root cause was that Validated PR diff and checks: Unit Tests, Tower Integration Tests, CLI Integration Tests, Package Install Verification, and cross-platform CLI checks are all passing. Approved to merge. Architect review |
waleedkadous
approved these changes
May 7, 2026
Contributor
waleedkadous
left a comment
There was a problem hiding this comment.
Thank you so much for the fix! @otherview just a heads up.
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
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
Fixes #725
Root Cause
bridge-mode.test.tsspawns Tower viadist/agent-farm/servers/tower-server.js, but the unit-test CI job only builds@cluesmith/codev-core— it does not buildpackages/codev/dist/. The test was being picked up by the default vitest config and failing with "Cannot find module".Fix
Renamed
bridge-mode.test.ts→bridge-mode.e2e.test.ts, which:vitest.config.ts(unit tests) via the existing**/*.e2e.test.tsexclude patternvitest.e2e.config.ts(integration tests) via the existingsrc/**/*.e2e.test.tsinclude pattern.e2e.test.tsfiles in the same directory already use this patternNo config changes needed. Zero-diff rename (file content unchanged).
Test Plan
vitest listconfirms bridge-mode is NOT in unit test listvitest list --config vitest.e2e.config.tsconfirms bridge-mode IS in integration test listvitest run --coveragepasses without bridge-mode (exit 0)