[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:
|
| Comments |
| Comment by Githook User [ 17/Apr/20 ] |
|
Author: {'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}Message: |
| 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: |