[JAVA-3098] Re-enable failing command monitoring tests on 4.2 Created: 21/Nov/18 Updated: 28/Oct/23 Resolved: 27/Feb/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Test Coverage |
| Affects Version/s: | None |
| Fix Version/s: | 3.11.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
The following command monitoring tests are failing on 4.1 latest build:
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 [ 27/Feb/19 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Fix and re-enable failing command monitoring tests on MongoDB 4.2+ Make the tests pass again by ignoring extra fields in the writeError
|
| Comment by Githook User [ 14/Jan/19 ] |
|
Author: {'username': 'jyemin', 'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin'}Message: Disable command monitoring tests failing against 4.1 server
|
| Comment by Githook User [ 21/Nov/18 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com', 'username': 'jyemin'}Message: Disable command monitoring tests failing against 4.1 server
|