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

Remove the config_fuzzer_concurrency_sharded_replication suite from the test Windows DEBUG builder

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2023-05-15
    • 150

    Description

      The linked test failure is happening a lot on Windows DEBUG builder only. That particular suite is very slow, and that builder makes it slower, and is also a relatively expensive builder to run.

      I also recommend removing all the *concurrency_sharded_replication test suites from the builder. It's a known slow builder, where we primarily don't have failures in concurrency suites due to code logic issues, just test failures due to a fundamentally slow concurrency suite running on a machine that has a level of detail that makes things even slower, pushing the timeout boundary frequently.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: