[SERVER-72962] Use higher maxTimeMS in transaction API unit test Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 19/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding NYC 2023-01-23 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
Transaction API test MaxTimeMSIsSetIfOperationContextHasDeadlineAndIgnoresDefaultRetryLimit verifies the retry limit is ignored if a maxTimeMS has been set. It uses a maxTimeMS of 2 seconds and does not expect it to be reached, but that value is too low and can be hit on a slow machine, leading to a spurious failure. The value should be raised to make the test more resilient. |
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |