Exclude Vector Search index from cloud invariant tests#5711
Merged
Conversation
The vector_search_index variant dominates the cloud -short invariant run: a VS index takes 10-20 min to create and the invariant tests deploy it twice (deploy, then re-plan), a major contributor to the suite timing out. The dedicated vector_search_indexes resource test already covers it on cloud (CloudSlow), so exclude it from no_drift on cloud. Also exclude it entirely from continue_293, where v0.293.0 cannot deploy it anyway. Co-authored-by: Isaac
Collaborator
Integration test reportCommit: 2a6de76
22 interesting tests: 13 SKIP, 7 RECOVERED, 2 flaky
Top 5 slowest tests (at least 2 minutes):
|
andrewnester
approved these changes
Jun 25, 2026
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
3 participants
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.
The
vector_search_indexvariant dominates the cloud-shortinvariant run — a VS index takes 10–20 min to create and the invariant tests deploy it twice (deploy, then re-plan), a major contributor to the suite timing out and starving later tests.The dedicated
vector_search_indexesresource test already covers it on cloud (CloudSlow/nightly), so this excludes it fromno_drifton cloud (kept locally, where it's fast against the mock). It also excludes it entirely fromcontinue_293, where v0.293.0 can't deploy it anyway — the index config embeds an endpoint, and Vector Search resources aren't supported on v0.293.0.migratealready excluded it (no terraform converter).This pull request and its description were written by Isaac.