chore: reenable smoketest COMPASS-9554 #7169
Merged
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
paula-stacho
force-pushed
the
try-reenable-test
branch
from
34b7b5d to
f2e6838
Compare
There was a problem hiding this comment.
Pull Request Overview
This PR re-enables a previously skipped smoke test by removing a Windows-specific skip condition. The test "can open compass, connect to a database and run a query on a collection (second run onwards)" was previously disabled on Windows due to flakiness issues, but appears to be stable now.
- Removes Windows platform check that was skipping the test
- Re-enables the time-to-first-query smoke test for all platforms
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
paula-stacho
changed the title
gribnoysup
approved these changes
Aug 13, 2025
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.
Looks like it's not as flaky atm (I've tried several runs), let's try re-enabling the test. If it starts failing too often we can prioritize https://jira.mongodb.org/browse/COMPASS-9554, maybe add the 1st responder label so that it gets looked into soon.