microsoft/openvmm

Public

mirrored fromhttps://github.com/microsoft/openvmmAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
c01ec12f86320d4891b338c5d03782231410c380

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

.config/nextest.toml

50lines · modecode

1# Copyright (c) Microsoft Corporation.
2# Licensed under the MIT License.
3
4[[profile.default.overrides]]
5filter = '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.
9threads-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
14filter = 'package(~vmm_tests) and test(openhcl)'
15# Mark OpenHCL VMM tests as extra heavy, as they have to also simulate VTL2.
16threads-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
21slow-timeout = { period = "1s", terminate-after = 5 }
22# Print out output for failing tests as soon as they fail, and also at the end
23# of the run (for easy scrollability).
24failure-output = "immediate-final"
25# Do not cancel the test run on the first failure.
26fail-fast = false
27
28[profile.ci.junit]
29path = "junit.xml"
30store-success-output = "true"
31
32[[profile.ci.overrides]]
33# use fuzzy-matching for the package() to allow out-of-tree tests to use the
34# same profile
35filter = 'package(~vmm_tests)'
36# Allow VMM tests longer timeouts.
37# Important Note: Petri's watchdogs need to know this value too.
38# If you change it here then change it there!
39slow-timeout = { period = "3m", terminate-after = 2 }
40
41# TEMP (hopefully): For reasons that continue to befuddle, running Windows
42# release-mode unit tests in flowey CI is resulting in seemingly-random
43# tests occationally stalling by up to ~10 seconds.
44#
45# This did not occur in the "legacy" non-flowey CI, and so the question becomes:
46# what subtle different in execution environments between the new pipeline and
47# the old pipeline is causing this different behavior?
48[[profile.ci.overrides]]
49platform = 'cfg(windows)'
50slow-timeout = { period = "1s", terminate-after = 30 }
51