[SERVER-26864] Use duration ctor for asio timer in NIA setAlarm Created: 01/Nov/16 Updated: 19/Nov/16 Resolved: 07/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Cotter | Assignee: | Matt Cotter |
| Resolution: | Done | 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: | Platforms 2016-11-21 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
NetworkInterfaceASIO currently creates timers for setAlarm using an absolute time point rather than a duration. Our tests were switched to use mock timers, and this is resulting in taking a mock timer time point and setting an expiry as though it was a time point on the system clock. Switching setAlarm to use durations relative to NetworkInterfaceASIO::now() will fix this issue in our test. |
| Comments |
| Comment by Githook User [ 07/Nov/16 ] |
|
Author: {u'username': u'Machyne', u'name': u'Matt Cotter', u'email': u'matt.cotter@mongodb.com'}Message: |