[SERVER-39308] Update burn_in_tests.py to generate sub-tasks JSON file Created: 31/Jan/19 Updated: 29/Oct/23 Resolved: 06/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2019-03-11 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
Modify burn_in_tests.py to support the following new option
|
| Comments |
| Comment by Githook User [ 06/Mar/19 ] |
|
Author: {'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com', 'username': 'hptabster'}Message: |
| Comment by Jonathan Abrahams [ 25/Feb/19 ] |
|
It makes more sense to use the --generateTasksFile option to specify the output file name i.e., burn_in_tests.json. It will default to None. |
| Comment by Jonathan Abrahams [ 31/Jan/19 ] |
|
The burn_in_tests.json file contains the definition used to run sub-tasks. This file is created when the --generateTasksFile option is specified. If this option is not specified, then burn_in will operate as it already does. The sub-tasks JSON file will contain the commands for each task as follows. The generated sub-task names will be identifiable as burn_in, such that it's queryable, i.e., burn_in:<sub_task_name>. The sub_task name will be constructed as follows: <variant><task_name><task_number>:
Example, burn_in:enterprise-rhel-62-64-bit_jsCore_0000 The sub-tasks JSON file will also contain a display_tasks section which groups all the execution tasks under the name burn_in_tests. |