-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
Observed here:
With logs:
[2020/06/29 18:06:47.523] Test path: /data/mci/0301e2be9f12986bcb452a984b8594ad/mongo-cxx-driver/build/
[2020/06/29 18:06:47.523] ../data/crud/v2/aggregate-merge.json
[2020/06/29 18:06:47.523] Test description: Aggregate with $merge and majority readConcern
[2020/06/29 18:06:47.523] Operation: { "object" : "collection", "name" : "aggregate",
[2020/06/29 18:06:47.523] "collectionOptions" : { "readConcern" : { "level" : "majority" } },
[2020/06/29 18:06:47.523] "arguments" : { "pipeline" : [ { "$sort" : { "x" : 1 } }, { "$match" : {
[2020/06/29 18:06:47.523] "_id" : { "$gt" : 1 } } }, { "$merge" : { "into" : "other_test_collection" }
[2020/06/29 18:06:47.523] } ] } }
[2020/06/29 18:06:47.523] Had more expected documents than we found.
[2020/06/29 18:06:47.524] ===============================================================================
I believe this is because the test is inserting the setup "data" with default write concern instead of write concern majority. libmongoc inserts with write concern majority. The transactions test runner readme says to insert with write concern majority.