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

unittests ran for more than an hour, stalling the commit queue

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • STM 2020-10-05, STM 2020-10-19, STM 2020-11-02, STM 2020-11-16

      The task was https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_dynamic_required_unittests_patch_ce6cfc30df7f5545e19a2cdf84b94777eaa3b4de_5f43f20761837d41a450fbb6_20_08_24_18_30_02. It was aborted in order to get the queue going again.

      acm suggested a shorter timeout in the commit queue.

      brian.samek wonders if there should be shorter timeouts for the unittests regardless of whether they run in the commit queue or elsewhere. If they only time out in the commit queue but not in mainline builds, the hangs may not be investigated.

            Assignee:
            richard.samuels@mongodb.com Richard Samuels (Inactive)
            Reporter:
            brian.samek@mongodb.com Brian Samek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: