-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2024-10-28, Repl 2024-11-11, Repl 2024-12-09, Repl 2024-12-23
We have several very similar passthroughs which make patch builds expensive, both in terms of time and cost:
- replica_sets_jscore_passthrough
- replica_sets_fcbis_jscore_passthrough
- replica_sets_initsync_jscore_passthrough
- replica_sets_kill_secondaries_jscore_passthrough
- replica_sets_reconfig_jscore_passthrough
- replica_sets_terminate_primary_jscore_passthrough
- .... many many more
Let's see if it's possible to combine some of these. The one thing we need to be wary of is some of the more advanced passthroughs exclude tests. In the process of consolidating suites we should make sure that we don't permanently exclude some tests from ever running, as now those tests have no suite to run in.
Note that this is different from SERVER-76991 ("create kitchen sink suite"). The goal of that ticket is to create a suite that bombards the server to test it more thoroughly. The primary goal of this ticket is to reduce the number of passthroughs.
- is related to
-
SERVER-76991 Create a "kitchen sink" suite
- Open
- related to
-
SERVER-97604 Investigate if replica_sets_initsync_static_jscore_passthrough can be removed (from required build or deleted)
- Open