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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.8
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2019-02-11
    • Linked BF Score:
      18

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: