[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:
Backports
Depends
Duplicate
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: SERVER-41585 Modified background_thread_clock_source_test to not assume we can schedule the background thread

(cherry picked from commit fd128764a9e127907e2d73d6104a80612f507596)
Branch: v4.2
https://github.com/mongodb/mongo/commit/57febb037cd1b173d35656653989664b3b630469

Comment by Githook User [ 28/Jun/19 ]

Author:

{'name': 'Shaileja Jain', 'username': 'shailejajain', 'email': 'shaileja.jain@gmail.com'}

Message: SERVER-41585 Modified background_thread_clock_source_test to not assume we can schedule the background thread
Branch: master
https://github.com/mongodb/mongo/commit/fd128764a9e127907e2d73d6104a80612f507596

Generated at Thu Feb 08 04:58:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.