diff options
| author | Eddie Louie <eddie.louie@mongodb.com> | 2017-05-25 09:58:55 -0400 |
|---|---|---|
| committer | Eddie Louie <eddie.louie@mongodb.com> | 2017-05-30 12:13:26 -0400 |
| commit | 7a5e180130dd464a9d74bef1442e3a767f9dfbdc (patch) | |
| tree | acf531e8cf3b5ef7e66ca03be75439043a30f600 /etc/test_retrial.yml | |
| parent | 50ea467d27c8ec98ee25d8298d61e0d5edfc560e (diff) | |
| download | mongo-7a5e180130dd464a9d74bef1442e3a767f9dfbdc.tar.gz | |
SERVER-29060 Add etc/test_retrial.yml resmoke.py tag file
Diffstat (limited to 'etc/test_retrial.yml')
| -rw-r--r-- | etc/test_retrial.yml | 48 |
1 files changed, 48 insertions, 0 deletions
diff --git a/etc/test_retrial.yml b/etc/test_retrial.yml new file mode 100644 index 00000000000..4d7e491c0fd --- /dev/null +++ b/etc/test_retrial.yml @@ -0,0 +1,48 @@ +# This file is used to tag JS tests for retry on failure that run in the mainline. +# +# For JS tests that have failed, you can tag them to be retried. The following scenarios apply: +# +# 1. the test sometimes fails in any task on any build variant with any distro, +# 2. the test sometimes fails in a specific task on any build variant with any distro, +# 3. the test sometimes fails in a specific task on a specific build variant with any distro, or +# 4. the test sometimes fails in a specific task on a specific build variant with a specific distro. +# +# Depending on which of the above scenarios apply, you can tag the JS file with the following tags, +# respectively. +# +# 1. retry_on_failure +# 2. retry_on_failure|${task_name} +# 3. retry_on_failure|${task_name}|${build_variant} +# 4. retry_on_failure|${task_name}|${build_variant}|${distro_id} +# +# Examples: +# +# JS test failed: jstests/sharding/exact_shard_key_target.js +# in task_name: sharding_csrs_continuous_config_stepdown_WT +# on build_variant: any +# with distro_id: any +# tag with: retry_on_failure|sharding_csrs_continuous_config_stepdown_WT +# +# JS test failed: jstests/noPassthrough/backup_restore_stop_start.js +# in task_name: noPassthrough +# on build_variant: enterprise-rhel-62-64-bit +# with distro_id: rhel62-small +# tag with: retry_on_failure|noPassthrough|enterprise-rhel-62-64-bit|rhel62-small +# +# Example of tagging a test affecting multiple tasks: +# +# JS test failed: jstests/sharding/shard_collection_verify_initial_chunks.js +# in task_name: sharding and sharding_WT +# on build_variant: linux-64 +# with distro_id: any +# tag with: retry_on_failure|sharding|linux-64 and +# retry_on_failure|sharding_WT|linux-64 +# +# +# Note: Making it possible to ignore test failures increases the risk we won't (or will take +# longer to) discover a bug and therefore tests should be tagged judiciously. + +selector: + js_test: + # jstests/sharding/exact_shard_key_target.js: + # - retry_on_failure|sharding_csrs_continuous_config_stepdown_WT |