-
Type:
Engineering Test
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Replication
-
Fully Compatible
-
Repl 2026-04-13
-
None
-
None
-
None
-
None
-
None
-
None
-
None
On our side we now define 20 different tasks to run on antithesis here. But looking at the history of our "Core Server Test" runs, I only see 12 different tasks being run.
The tasks that we don't run:
1. antithesis_jstestfuzz_sharded_with_config_transitions
2. antithesis_concurrency_sharded_stepdown_terminate_kill_primary_with_balancer_config_shard
3. antithesis_config_fuzzer_concurrency_sharded_replication
4. antithesis_core
5. antithesis_jstestfuzz_sharded
6. antithesis_replica_sets_basic_js_commands
7. antithesis_sharding_basic_js_commands
We should remove these tasks from our tasks definition so as to not confuse the reader, since we're not actually executing them. The source of truth of which tasks are run is on the antithesis side.
- is related to
-
SERVER-123169 Antithesis: make composer tests work
-
- Needs Scheduling
-