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

The sharding unit-tests' `kFutureTimeout` duration is too short for slow variants

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.8
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2019-02-11
    • 18

      The sharding unit-tests, which spawn asynchronous activities via launchAsync wait for up to kFutureTimeout = 5 seconds for these activities to complete. Some of these tasks however may perform database writes and other storage engine operations and on slower variants, such as DEBUG on arm64, this may take more than 5 seconds.

      In order to make these tests more robust on slower variants we should increase this constant to 15 seconds.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: