[GODRIVER-1558] Investigate $merge test failures Created: 06/Apr/20  Updated: 28/Oct/23  Resolved: 22/Apr/20

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.0

Type: Task Priority: Major - P3
Reporter: Divjot Arora (Inactive) Assignee: Divjot Arora (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Our waterfall shows various failures relating to aggregates with $merge stages. Thoughts on what could be causing them:

 

  1. Documents/failpoints aren't being written with a high enough writeconcern.
  2. Documents aren't being read with a high enough read concern.
  3. Data from previous tests isn't being cleaned up and is conflicting with these tests.


 Comments   
Comment by Githook User [ 17/Apr/20 ]

Author:

{'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}

Message: GODRIVER-1558 Sort on _id when verifying collections in tests (#375)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/3d1b780844d6fcf2788176b1578787a00ece9718

Comment by Divjot Arora (Inactive) [ 17/Apr/20 ]

Additional logging shows that the tests are sometimes failing because the find on the outcome collection returns results in a different order than expected by the spec test. PR https://github.com/mongodb/mongo-go-driver/pull/375 changes the find to sort on _id to ensure that the documents are in the same order. After that PR is merged, I'm going to leave this ticket open for a bit and monitor the waterfall to see if we find any other issues that could be related.

Comment by Githook User [ 16/Apr/20 ]

Author:

{'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}

Message: GODRIVER-1558 Ensure topology kind is always discovered for integration tests (#373)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/891a5fc9374a3e31b8fc9e7117bb690d640edff6

Generated at Thu Feb 08 08:36:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.