|
| 1 | +# This is based on the default config used by nextest. It is embedded in the binary at |
| 2 | +# build time. It may be used as a template for .config/nextest.toml. |
| 3 | + |
| 4 | +[store] |
| 5 | +# The directory under the workspace root at which nextest-related files are |
| 6 | +# written. Profile-specific storage is currently written to dir/<profile-name>. |
| 7 | +dir = "target/nextest" |
| 8 | + |
| 9 | +[test-groups] |
| 10 | +serial-integration = { max-threads = 1 } |
| 11 | + |
| 12 | +# This section defines the default nextest profile. Custom profiles are layered |
| 13 | +# on top of the default profile. |
| 14 | +[profile.default] |
| 15 | +# "retries" defines the number of times a test should be retried. If set to a |
| 16 | +# non-zero value, tests that succeed on a subsequent attempt will be marked as |
| 17 | +# non-flaky. Can be overridden through the `--retries` option. |
| 18 | +# Examples |
| 19 | +# * retries = 3 |
| 20 | +# * retries = { backoff = "fixed", count = 2, delay = "1s" } |
| 21 | +# * retries = { backoff = "exponential", count = 10, delay = "1s", jitter = true, max-delay = "10s" } |
| 22 | +retries = 0 |
| 23 | + |
| 24 | +# The number of threads to run tests with. Supported values are either an integer or |
| 25 | +# the string "num-cpus". Can be overridden through the `--test-threads` option. |
| 26 | +test-threads = "num-cpus" |
| 27 | + |
| 28 | +# The number of threads required for each test. This is generally used in overrides to |
| 29 | +# mark certain tests as heavier than others. However, it can also be set as a global parameter. |
| 30 | +threads-required = 1 |
| 31 | + |
| 32 | +# Show these test statuses in the output. |
| 33 | +# |
| 34 | +# The possible values this can take are: |
| 35 | +# * none: no output |
| 36 | +# * fail: show failed (including exec-failed) tests |
| 37 | +# * retry: show flaky and retried tests |
| 38 | +# * slow: show slow tests |
| 39 | +# * pass: show passed tests |
| 40 | +# * skip: show skipped tests (most useful for CI) |
| 41 | +# * all: all of the above |
| 42 | +# |
| 43 | +# Each value includes all the values above it; for example, "slow" includes |
| 44 | +# failed and retried tests. |
| 45 | +# |
| 46 | +# Can be overridden through the `--status-level` flag. |
| 47 | +status-level = "pass" |
| 48 | + |
| 49 | +# Similar to status-level, show these test statuses at the end of the run. |
| 50 | +final-status-level = "flaky" |
| 51 | + |
| 52 | +# "failure-output" defines when standard output and standard error for failing tests are produced. |
| 53 | +# Accepted values are |
| 54 | +# * "immediate": output failures as soon as they happen |
| 55 | +# * "final": output failures at the end of the test run |
| 56 | +# * "immediate-final": output failures as soon as they happen and at the end of |
| 57 | +# the test run; combination of "immediate" and "final" |
| 58 | +# * "never": don't output failures at all |
| 59 | +# |
| 60 | +# For large test suites and CI it is generally useful to use "immediate-final". |
| 61 | +# |
| 62 | +# Can be overridden through the `--failure-output` option. |
| 63 | +failure-output = "immediate" |
| 64 | + |
| 65 | +# "success-output" controls production of standard output and standard error on success. This should |
| 66 | +# generally be set to "never". |
| 67 | +success-output = "never" |
| 68 | + |
| 69 | +# Cancel the test run on the first failure. For CI runs, consider setting this |
| 70 | +# to false. |
| 71 | +fail-fast = true |
| 72 | + |
| 73 | +# Treat a test that takes longer than the configured 'period' as slow, and print a message. |
| 74 | +# See <https://nexte.st/book/slow-tests> for more information. |
| 75 | +# |
| 76 | +# Optional: specify the parameter 'terminate-after' with a non-zero integer, |
| 77 | +# which will cause slow tests to be terminated after the specified number of |
| 78 | +# periods have passed. |
| 79 | +# Example: slow-timeout = { period = "60s", terminate-after = 2 } |
| 80 | +slow-timeout = { period = "60s" } |
| 81 | + |
| 82 | +# Treat a test as leaky if after the process is shut down, standard output and standard error |
| 83 | +# aren't closed within this duration. |
| 84 | +# |
| 85 | +# This usually happens in case of a test that creates a child process and lets it inherit those |
| 86 | +# handles, but doesn't clean the child process up (especially when it fails). |
| 87 | +# |
| 88 | +# See <https://nexte.st/book/leaky-tests> for more information. |
| 89 | +leak-timeout = "100ms" |
| 90 | + |
| 91 | +[profile.default.junit] |
| 92 | +# Output a JUnit report into the given file inside 'store.dir/<profile-name>'. |
| 93 | +# If unspecified, JUnit is not written out. |
| 94 | + |
| 95 | +# path = "junit.xml" |
| 96 | + |
| 97 | +# The name of the top-level "report" element in JUnit report. If aggregating |
| 98 | +# reports across different test runs, it may be useful to provide separate names |
| 99 | +# for each report. |
| 100 | +report-name = "nextest-run" |
| 101 | + |
| 102 | +# Whether standard output and standard error for passing tests should be stored in the JUnit report. |
| 103 | +# Output is stored in the <system-out> and <system-err> elements of the <testcase> element. |
| 104 | +store-success-output = false |
| 105 | + |
| 106 | +# Whether standard output and standard error for failing tests should be stored in the JUnit report. |
| 107 | +# Output is stored in the <system-out> and <system-err> elements of the <testcase> element. |
| 108 | +# |
| 109 | +# Note that if a description can be extracted from the output, it is always stored in the |
| 110 | +# <description> element. |
| 111 | +store-failure-output = true |
| 112 | + |
| 113 | +[[profile.default.overrides]] |
| 114 | +# `is_probably_prime` test heavily use rdrand, sometimes the VM where test is running has shortage on it |
| 115 | +filter = 'test(is_probably_prime)' |
| 116 | +retries = { backoff = "exponential", count = 6, delay = "1s", jitter = true } |
| 117 | +test-group = 'serial-integration' |
| 118 | + |
0 commit comments