Increase the default timeout for unit-tests which schedule work through `NetworkTestEnv::launchAsync`

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10, 4.0.27
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v4.0
    • Sharding 2019-03-25
    • 44
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Unit-tests, which schedule asynchronous work through NetworkTestEnv::launchAsync currently wait for up to 15 seconds for that work to complete.

      On DEBUG builds and on slower Evergreen machine variants we have seen this async work take more than 15 seconds, causing the unit-tests to fail. In order to avoid these intermittent failures, we should increase this default timeout to be on the order of a few minutes (I'd say 5 minutes is a good round number).

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: