diff options
Diffstat (limited to 'docs/evergreen-testing/burn_in_tags.md')
| -rw-r--r-- | docs/evergreen-testing/burn_in_tags.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/evergreen-testing/burn_in_tags.md b/docs/evergreen-testing/burn_in_tags.md new file mode 100644 index 00000000000..579f432efc4 --- /dev/null +++ b/docs/evergreen-testing/burn_in_tags.md @@ -0,0 +1,19 @@ +# burn_in_tags + +## What it is + +Similar to [burn_in_tests](burn_in_tests.md), `burn_in_tags` also detects the javascript tests +(under the [jstests directory](https://github.com/mongodb/mongo/tree/master/jstests)) +that are new or have changed since the last git command and then runs those tests in repeated +mode to validate their stability. But instead of running the tests on their original build +variants, `burn_in_tags` runs them on the burn_in build variants that are generated separately. + +## How to use it + +You can use `burn_in_tags` on evergreen by selecting the `burn_in_tags_gen` task when creating a patch. +The burn_in build variants, i.e., `enterprise-rhel-80-64-bit-inmem` and `enterprise-rhel-80-64-bit-multiversion` +will be generated, each of which will have a `burn_in_tests` task generated by the +[mongo-task-generator](https://github.com/mongodb/mongo-task-generator). `burn_in_tests` task, a +[generated task](task_generation.md), may have multiple sub-tasks which run the test suites only for the +new or changed javascript tests (note that a javascript test can be included in multiple test suites). Each of +those tests will be run 2 times minimum, and 1000 times maximum or for 10 minutes, whichever is reached first. |