[CDRIVER-2975] Resync transaction spec tests for bulk write error reporting change Created: 21/Feb/19  Updated: 10/Jan/24  Resolved: 09/Aug/19

Status: Closed
Project: C Driver
Component/s: libmongoc, tests
Affects Version/s: None
Fix Version/s: 1.15.0

Type: New Feature Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Samantha Ritter (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-609 Resync transaction spec tests for bul... Closed
Gantt Dependency
has to be done after CDRIVER-2883 Support sharded transactions recovery... Closed
has to be done after CDRIVER-3215 Specify effect of client-side errors ... Closed
Related
related to CDRIVER-4811 Failing errorContains assertion in ca... Backlog
is related to CDRIVER-4806 Require 4.3.1+ server version when us... Closed
Epic Link: C 4.2 Support

 Description   

See DRIVERS-609 for details.



 Comments   
Comment by Githook User [ 10/Jan/24 ]

Author:

{'name': 'Jeremy Mikola', 'email': 'jmikola@gmail.com', 'username': 'jmikola'}

Message: CDRIVER-4806 sync tests for failCommand errorLabels reqs (#1508)

Synced with mongodb/specifications@5fc23f40f79d18f0693e7159eba81f0e7b276715

Updates retryable writes prose test 3 to relocate the errorLabels field when configuring a fail point.

Note: with_transaction/callback-retry.json is unrelated but was missed in CDRIVER-2975. This test currently fails and has been skipped (see: CDRIVER-4811).
Branch: master
https://github.com/mongodb/mongo-c-driver/commit/4ef84ecdb7f1ce86b3d96b34ef8015d9c5f0f3f1

Comment by Jeremy Mikola [ 04/Jan/24 ]

This missed syncing mongodb/specifications@f5983a4 from SPEC-1221; however, that will be pulled in by CDRIVER-4806.

Comment by Kevin Albertson [ 09/Aug/19 ]

Done as part of CDRIVER-3287.

Comment by Samantha Ritter (Inactive) [ 23/Jul/19 ]

There are a few other ticket items that should be done before we sync the new transaction tests. Otherwise, the amount of "skipReason" statements we would need to add in are excessive. I've linked some of those tickets, though there may be more, to this one.

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