-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
Currently, modifying multiversion testing behavior can be risky. For instance, SERVER-65937 is a bug where multiversion suites were not running all tests that they should be, leading to test coverage gaps. We should investigate solutions to make modifying multiversion code less risky.
- duplicates
-
SERVER-64361 Add the "future git tag multiversion" variant to the patch build process
- Backlog
- related to
-
SERVER-65937 JS tests tagged with requires_fcv_53 do not run in the implicit multiversion passthroughs on the 6.0 branch
- Closed
-
SERVER-66034 backports_required_for_multiversion_tests.yml is not blacklisting tenant migration tests from running on multiversion test suites
- Closed