microsoft/openvmm
Publicmirrored fromhttps://github.com/microsoft/openvmmAvailable
.config/nextest.toml
49lines · modecode
| 1 | # Copyright (c) Microsoft Corporation. |
| 2 | # Licensed under the MIT License. |
| 3 | |
| 4 | [[profile.default.overrides]] |
| 5 | filter = 'package(~vmm_tests)' |
| 6 | # Mark VMM tests as heavy and requiring more threads due to their memory and CPU |
| 7 | # usage. For local dev runs, you may need to manually restrict the number of |
| 8 | # threads running via the -j cli arg. |
| 9 | threads-required = 2 |
| 10 | |
| 11 | [[profile.default.overrides]] |
| 12 | # use fuzzy-matching for the package() to allow out-of-tree tests to use the |
| 13 | # same profile |
| 14 | filter = 'package(~vmm_tests) and test(openhcl)' |
| 15 | # Mark OpenHCL VMM tests as extra heavy, as they have to also simulate VTL2. |
| 16 | threads-required = 4 |
| 17 | |
| 18 | # Profile for CI runs. |
| 19 | [profile.ci] |
| 20 | # Set the default timeout to 1 second, with tests terminated after 5 seconds |
| 21 | slow-timeout = { period = "1s", terminate-after = 5 } |
| 22 | # Print out output for failing tests at the end of the run. |
| 23 | failure-output = "final" |
| 24 | # Do not cancel the test run on the first failure. |
| 25 | fail-fast = false |
| 26 | |
| 27 | [profile.ci.junit] |
| 28 | path = "junit.xml" |
| 29 | store-success-output = "true" |
| 30 | |
| 31 | [[profile.ci.overrides]] |
| 32 | # use fuzzy-matching for the package() to allow out-of-tree tests to use the |
| 33 | # same profile |
| 34 | filter = 'package(~vmm_tests)' |
| 35 | # Allow VMM tests longer timeouts. |
| 36 | # Important Note: Petri's watchdogs need to know this value too. |
| 37 | # If you change it here then change it there! |
| 38 | slow-timeout = { period = "3m", terminate-after = 2 } |
| 39 | |
| 40 | # TEMP (hopefully): For reasons that continue to befuddle, running Windows |
| 41 | # release-mode unit tests in flowey CI is resulting in seemingly-random |
| 42 | # tests occationally stalling by up to ~10 seconds. |
| 43 | # |
| 44 | # This did not occur in the "legacy" non-flowey CI, and so the question becomes: |
| 45 | # what subtle different in execution environments between the new pipeline and |
| 46 | # the old pipeline is causing this different behavior? |
| 47 | [[profile.ci.overrides]] |
| 48 | platform = 'cfg(windows)' |
| 49 | slow-timeout = { period = "1s", terminate-after = 30 } |