-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Decision Automation Group
-
Fully Compatible
-
ALL
-
DAG 2023-09-18
-
2
buildscripts/burn_in_tests.py generate-test-membership-map-file-for-ci generates the association of a particular JavaScript test file and all of the resmoke YAML suite files the test would run under. However the decision about whether a test is suitable to run depends on the state of resmokelib.config.EXCLUDE_WITH_ANY_TAGS which in particular is populated by the names of all of the in-development feature flags unless --runAllFeatureFlagTests is specified.
- https://github.com/mongodb/mongo/blob/4eafd09451f63372ca48ea57dd568763b60338cf/buildscripts/resmokelib/configure_resmoke.py#L205-L206
- https://github.com/mongodb/mongo/blob/4eafd09451f63372ca48ea57dd568763b60338cf/buildscripts/resmokelib/configure_resmoke.py#L241-L246
The buildscripts/burn_in_tests.py script does not enable the --runAllFeatureFlagTests mode of resmoke and so these tests are currently never run by burn_in_tests. This defeats a large portion of the use case for burn_in_tests because engineers are writing new tests for their projects under an in-development feature flag and means these JavaScript test files won't be stressed to determine if the tests are unreliable.
- is duplicated by
-
SERVER-81001 burn_in_tests does not correctly determine which suites to run for a specific test
- Closed
- is related to
-
SERVER-54420 Add feature flag checker to generated multiversion tests
- Closed
-
SERVER-72928 Expand burn-in-tags to all required & suggested variants
- Closed