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

NetworkInterfaceTest needs to be more permissive with async op timeout

    • Service Arch
    • Fully Compatible
    • ALL
    • v7.0, v6.3, v6.0, v5.0, v4.4
    • Service Arch 2023-07-10, Service Arch 2023-07-24
    • 0

      Here and here, we compare the elapsed time from the NetworkInterfaceTL with fixed values. However, the NetworkInterfaceTL measures its result from when it started the command. We should use OperationContext::setDeadlineByDate(...) instead of OperationContext:: setDeadlineAfterNowBy(...) and record the delay from our source data (without additional timeout) until after we invoke runCommand(). We can then compare the elapsed time with the timeouts minus the delay.

            Assignee:
            vojislav.stojkovic@mongodb.com Vojislav Stojkovic
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: