GODRIVER-2248 Use mock deployment for slow BulkWrite update test #827
Conversation
This file contains 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
benjirewis
commented
Dec 14, 2021
benjirewis
added a commit
that referenced
this pull request
Mar 1, 2022
benjirewis
added a commit
that referenced
this pull request
Mar 1, 2022
faem
pushed a commit
to kubedb/mongo-go-driver
that referenced
this pull request
Mar 17, 2022
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.
GODRIVER-2248
TestCollection/bulk_write/update_with_batcheswas causing timeouts on most of our MacOS variants. This was because of the large (100050) amount of documents that needed to be deleted server-side after the test. As in GODRIVER-1858, I've used the mock deployment built intomtestto lower testing times (from about 1m to about .3s).