diff options
author | David Bradford <david.bradford@mongodb.com> | 2022-03-02 15:26:04 -0500 |
---|---|---|
committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2022-03-02 20:57:30 +0000 |
commit | d883e3e0c216f10f7a1368bdd9d59316c32d2cd6 (patch) | |
tree | f7543323cdfa346158df9d4c0de9caf6e807655d /docs | |
parent | 5946ea0bf2aa23ae1021a626238a4d7809728bc2 (diff) | |
download | mongo-d883e3e0c216f10f7a1368bdd9d59316c32d2cd6.tar.gz |
Revert "SERVER-63827: Determine task timeout at the start of task execution"
This reverts commit 4080bd69384735eb49eb1799734d1bf8c93feb09.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/evergreen-testing/index.md | 5 | ||||
-rw-r--r-- | docs/evergreen-testing/task_timeouts.md | 35 |
2 files changed, 0 insertions, 40 deletions
diff --git a/docs/evergreen-testing/index.md b/docs/evergreen-testing/index.md deleted file mode 100644 index f57692ade9a..00000000000 --- a/docs/evergreen-testing/index.md +++ /dev/null @@ -1,5 +0,0 @@ -# Testing in Evergreen - -Documentation about how MongoDB is tested in Evergreen. - -* [Task Timeouts](task_timeouts.md) diff --git a/docs/evergreen-testing/task_timeouts.md b/docs/evergreen-testing/task_timeouts.md deleted file mode 100644 index e370aad22c9..00000000000 --- a/docs/evergreen-testing/task_timeouts.md +++ /dev/null @@ -1,35 +0,0 @@ -# Evergreen Task Timeouts - -## Type of timeouts - -There are two types of timeouts that [evergreen supports](https://github.com/evergreen-ci/evergreen/wiki/Project-Commands#timeoutupdate): - -* **Exec timeout**: The _exec_ timeout is the overall timeout for a task. Once the total runtime for -a test hits this value, the timeout logic will be triggered. This value is specified by -**exec_timeout_secs** in the evergreen configuration. -* **Idle timeout**: The _idle_ timeout is the amount of time in which evergreen will wait for -output to be created before it considers the task hung and triggers timeout logic. This value -is specified by **timeout_secs** in the evergreen configuration. - -**Note**: In most cases, **exec_timeout** is usually the more useful of the timeouts. - -## Setting the timeout for a task - -There are a few ways in which the timeout can be determined for a task running in evergreen. - -* **Specified in 'etc/evergreen.yml'**: Timeout can be specified directly in the 'evergreen.yml' file, -both on tasks and build variants. This can be useful for setting default timeout values, but is limited -since different build variants frequently have different runtime characteristics and it is not possible -to set timeouts for a task running on a specific build variant. - -* **etc/evergreen_timeouts.yml**: The 'etc/evergreen_timeouts.yml' file for overriding timeouts -for specific tasks on specific build variants. This provides a work-around for the limitations of -specifying the timeouts directly in the 'evergreen.yml'. In order to use this method, the task -must run the "determine task timeout" and "update task timeout expansions" functions at the beginning -of the task evergreen definition. Most resmoke tasks already do this. - -* **buildscripts/evergreen_task_timeout.py**: This is the script that reads the 'etc/evergreen_timeouts.yml' -file and calculates the timeout to use. Additionally, it will check the historic test results of the -task being run and see if there is enough information to calculate timeouts based on that. It can -also be used for more advanced ways of determining timeouts (e.g. the script is used to set much -more aggressive timeouts on tasks that are run in the commit-queue). |