Breakout db_s_shard_server_test into smaller targets to reduce time in commit queue unittests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • Fully Compatible
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      https://spruce.mongodb.com/version/688125f8b4e37700074993e0/task-duration?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

      Test that take longer than 100s are the following:

      //src/mongo/db/s:db_s_shard_server_test                                  PASSED in 411.7s
      //src/mongo/db/pipeline:db_pipeline_test                                 PASSED in 267.6s
      //src/mongo/db/repl:oplog_application_test                               PASSED in 210.8s
      //src/mongo/db/s:db_s_config_server_test                                 PASSED in 168.6s
      //src/mongo/util:util_test                                               PASSED in 157.6s
      //src/mongo/db/repl:db_repl_coordinator_test                             PASSED in 147.8s
      //src/mongo/db/repl:replication_recovery_test                            PASSED in 140.2s
      //src/mongo/db/storage/wiredtiger:storage_wiredtiger_test                PASSED in 113.9s
      //src/mongo/db/transaction:db_transaction_test                           PASSED in 106.0s
      

      The db_s_shard_server_test (in group4) is the longest overall and contains many many cpp test files that can be chunked apart to reduce waiting time on the longest runs.

              Assignee:
              Steve McClure
              Reporter:
              Steve McClure
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: