[SERVER-39931] sleep command should be willing to wait forever to acquire the lock Created: 01/Mar/19 Updated: 29/Oct/23 Resolved: 08/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 9 | ||||
| Description |
|
The (test-only) sleep command is designed to take a lock and sleep for a specified time while holding the lock. Currently it passes the maxTimeMS deadline as a deadline for acquiring a lock, which is leading to test failures. It should not do this - the lock acquisition is still interruptible by other means. |
| Comments |
| Comment by Githook User [ 08/Mar/19 ] |
|
Author: {'name': 'Charlie Swanson', 'username': 'cswanson310', 'email': 'charlie.swanson@mongodb.com'}Message: |