-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-03-17, CAR Team 2025-03-31, CAR Team 2025-04-14
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The single test jstests/sharding/mongos_writes_wait_for_write_concern_sharded.js takes 34 minutes in required patch builds. We should evaluate the structure of this testing because it stretches out the overall patch build completion time. Perhaps the test can avoid shutting down and restarting the mongod processes repeatedly and use failpoints or similar means on a live process instead?
- is depended on by
-
SERVER-103890 Lower default idle timeout for tasks on required build variants
-
- Blocked
-
- is related to
-
SERVER-98924 Improve test runtime of setWindowFields/n_accumulators.js when running under PQS fallback
-
- In Progress
-
-
SERVER-99462 Improve test runtime of timeseries/query/timeseries_group_aggregations.js
-
- Closed
-
-
SERVER-99778 Improve test runtime of jstests/noPassthrough/query/change_streams/change_stream_transaction.js
-
- Closed
-
-
SERVER-100528 Investigate all commands that accept write concern for WCE handling
-
- Closed
-
-
SERVER-103553 Improve test runtime of jstests/sharding/mongos_writes_wait_for_write_concern_timeseries.js
-
- Closed
-
- related to
-
SERVER-103559 Introduce default idle timeout for required build variants
-
- Closed
-
-
SERVER-102300 Improve test runtime of jstests/core/index/express_pbt.js
-
- Closed
-
-
SERVER-103698 Improve test runtime of jstests/sharding/mongos_writes_wait_for_write_concern_sharded.js and jstests/sharding/mongos_writes_wait_for_write_concern_timeseries.js (again)
-
- Closed
-