Revisit timeout of sharding_legacy_timeseries_no_rawdata suite

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-101589 we added more tests to the suites but we needed to force a larger `exec_timeout_secs` for the suite because the auto calculated one (300 secs) was too shorts. In fact, the jstests/sharding/mongos_writes_wait_for_write_concern_timeseries.js usually runs longer than 300 secs.

      The goal of the ticket is to remove the forced timeout and see if the automatic one have been adjusted to the long runtime of the problematic test.

            Assignee:
            Unassigned
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: