Skip to content

Use majority write concern and remove assert in change stream tests #1980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

kevinAlbs
Copy link
Collaborator

Summary

  • Use majority write concern to insert documents in test /change_stream/batchSize0.
  • Remove faulty assert in /change_stream/live/track_resume_token.

Background & Motivation

Using majority write concern is intended to address this observed test failure, which receives only one of two expected events.

The faulty assert removal follows mongodb/mongo-cxx-driver#1367, which made a similar change in the C++ driver test runner. I suspect the C++ tests were based off of the C driver tests.

@kevinAlbs kevinAlbs requested a review from eramongodb April 3, 2025 12:13
@eramongodb
Copy link
Contributor

Once merged, please cherry-pick onto the r2.0 and r1.30 release branches as well.

@kevinAlbs kevinAlbs merged commit 01d2ea0 into mongodb:master Apr 3, 2025
40 of 42 checks passed
kevinAlbs added a commit that referenced this pull request Apr 3, 2025
…1980)

* use majority write concern in change stream test

* do not assert that resume token changed after receiving no documents
kevinAlbs added a commit that referenced this pull request Apr 3, 2025
…1980)

* use majority write concern in change stream test

* do not assert that resume token changed after receiving no documents
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants