Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Service Arch
-
ALL
-
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:
- Using an alternative clock source (e.g., a mocked clock) that provides reliable results and is less susceptible to OS scheduling.
- 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.