[SERVER-54141] Propose a solution for timing issues in op_msg_integration_test Created: 29/Jan/21  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Amirsaman Memaripour Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Service Arch
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

Some of our integration tests in op_msg_integration_test.cpp rely on the system clock to measure elapsed time (see here for example). This approach heavily relies on the accuracy of the system clock, and is very fragile in presence of slow machines and other OS scheduling events.

This ticket should provide an alternative approach for writing these tests, potentially through one of the following options:

  1. Using an alternative clock source (e.g., a mocked clock) that provides reliable results and is less susceptible to OS scheduling.
  2. Rewriting the tests to remove reliance on timing as a measure of correctness.

The acceptance criteria for this ticket is:

  • A detailed action plan for addressing the timing issue in the integration test.
  • Filling follow-on tickets to fix the tests in op_msg_integration_test.cpp.


 Comments   
Comment by Lauren Lewis (Inactive) [ 18/Mar/22 ]

We haven’t heard back from you for some time, so we're going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:32:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.