Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-54141

Propose a solution for timing issues in op_msg_integration_test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 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:

      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.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: