[CSHARP-3687] Fixing legacy LINQ tests on latest Created: 25/May/21  Updated: 12/Aug/21  Resolved: 12/Aug/21

Status: Closed
Project: C# Driver
Component/s: Linq
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Dmitry Lukyanov (Inactive) Assignee: Robert Stam
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates CSHARP-3704 Temporarily disable tests failing due... Closed
Problem/Incident
is caused by SERVER-57300 {$exists:false} on array elements ret... Closed
Related
related to CSHARP-3704 Temporarily disable tests failing due... Closed

 Description   

Lately, some of legacy linq tests started to fail: https://evergreen.mongodb.com/task_log_raw/dot_net_driver_secure_tests__version~latest_os~windows_64_topology~standalone_auth~auth_ssl~ssl_test_net452_patch_5f4dafd4db327e15fd957d68f5f3e5188f681197_60aca6ded6d80a7ef55073e3_21_05_25_07_27_27/0?type=T#L1589.
Apparently something was changed on the server side since now tests can return more records than before (in one of tests that I checked, previously we return 4 documents, but now we have 5). This behavior was introduced recently so we should clarify the reason for this



 Comments   
Comment by Jeffrey Yemin [ 19/Jul/21 ]

Probably can just close this

Comment by James Kovacs [ 28/May/21 ]

The other test failures on 5.0-rc0 are variations on the above theme but performing a regex on an element in an array such as:

db.people.find({"a.0": {$not: /^T/}})
db.people.find({"a.0": {$not: /m$/}})
db.people.find({"a.0": {$not: /o/s}})

Comment by James Kovacs [ 28/May/21 ]

This appears to be a bug introduced in MongoDB 5.0. Details are in SERVER-57300. The short version is that

"_t.0": { $exists: false}

now returns incorrect results.

Generated at Wed Feb 07 21:46:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.