[SERVER-33129] getMinimumTimerResolution() returns maximum resolution on Windows Created: 05/Feb/18 Updated: 29/Oct/23 Resolved: 12/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.4, 3.7.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| 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 | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Platforms 2018-02-12 | ||||
| Participants: | |||||
| Description |
|
A logic error in getMinimumTimerResolution() causes it to return the maximum timer resolution (15 minutes) rather than the minimum timer resolution on Windows. |
| Comments |
| Comment by Githook User [ 01/Mar/18 ] |
|
Author: {'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams', 'username': 'jbreams'}Message: (cherry picked from commit af2632d719a31c250456dcfc3e840d5b52b293f5) |
| Comment by Githook User [ 12/Feb/18 ] |
|
Author: {'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams', 'username': 'jbreams'}Message: |