0
0
mirror of https://github.com/mongodb/mongo.git synced 2024-11-24 08:30:56 +01:00
mongodb/docs/evergreen-testing/burn_in_tests.md
Steve Gross 20fdd22b71 Revert "SERVER-82200 Update burn-in docs"
This reverts commit ef1b092437.

GitOrigin-RevId: d20a53ae1f488f29598715139b6ea6df48d43085
2024-01-29 17:46:50 +00:00

1.2 KiB

burn_in_tests

What it is

burn_in_tests detects the javascript tests (under the jstests directory) that are new or have changed since the last git command and then runs those tests in repeated mode to validate their stability.

How to use it

You can use burn_in_tests on evergreen by selecting the burn_in_tests_gen task when creating a patch, since burn_in_tests task is a generated task generated by the mongo-task-generator. burn_in_tests task will be generated on each of the applicable build variants, and 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.

You can also use burn_in_tests locally from within the mongo repo by running the script python buildscripts/burn_in_tests.py. For more information about this usage, you can run python buildscripts/burn_in_tests.py --help.