-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Decision Automation Group
-
2
When selected_tests runs a particular test because that test is related to the changed source file through test_mappings, it specifies a repeat argument (see here) in the same way that burn_in_tests does. (See example version here: https://evergreen.mongodb.com/version/5e385d1ba4cf473b25eabac9.) We built it this way because we were using the burn_in_tests code, but selected_tests_gen has no reason to repeat the tests, and no reason to use repeat arguments.
As a DAG engineer,
I should know that any tests that are run by tasks generated by selected_tests_gen do not have repeat-config-related arguments provided,
so the generated task config is as simple as possible and does not contain repeat arguments it doesn't need.
AC:
- no repeat-related arguments (i.e. --repeatSuites=1, --repeat=1) passed into resmoke by selected_tests_gen