[CSHARP-2444] Re-enable failing command monitoring tests on 4.2 Created: 29/Nov/18  Updated: 31/Mar/22

Status: Backlog
Project: C# Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Stam Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The following command monitoring tests are failing on 4.1 latest build:

  • A successful insert many command with write errors
  • A successful insert one command with write errors

due to a new field in the writeErrors documents describing the key pattern of the duplicate key violation. This ticket tracks both the disabling and re-enabling of these tests.



 Comments   
Comment by Githook User [ 13/Dec/18 ]

Author:

{'username': 'rstam', 'email': 'robert@robertstam.org', 'name': 'rstam'}

Message: CSHARP-2444: Rename SkipTestException SkipException after rebasing.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/4a818b21ea3411bd3d1405eb50161ac18997acc9

Comment by Robert Stam [ 29/Nov/18 ]

Blocked on resolution of how to handle unexpected fields in server response.

Comment by Githook User [ 29/Nov/18 ]

Author:

{'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}

Message: CSHARP-2444: Disable failing command monitoring tests on 4.2.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/3fb8b8bb9b06cba2cd463bb7c1a84d7e88f81685

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