[SERVER-41585] background_thread_clock_source_test shouldn't assume we can schedule the background thread Created: 07/Jun/19 Updated: 29/Oct/23 Resolved: 01/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Shaileja Jain (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||
| Sprint: | Service Arch 2019-07-01, Service Arch 2019-07-15 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 14 | ||||||||||||
| Description |
|
BF-12646 shows that sometimes we can fail to schedule the background thread clock source for >100ms (or that time moves backwards). I believe the fix here is to change the ASSERT_GT to a ASSERT_GTE (to account for failures to schedule) |
| Comments |
| Comment by Githook User [ 16/Aug/19 ] |
|
Author: {'name': 'Shaileja Jain', 'email': 'shaileja.jain@gmail.com', 'username': 'shailejajain'}Message: (cherry picked from commit fd128764a9e127907e2d73d6104a80612f507596) |
| Comment by Githook User [ 28/Jun/19 ] |
|
Author: {'name': 'Shaileja Jain', 'username': 'shailejajain', 'email': 'shaileja.jain@gmail.com'}Message: |