mirror of
https://github.com/servo/servo
synced 2026-04-25 17:15:48 +02:00
eca996ada3
This should help identify flaky unit tests, since codecov will gather statistics of tests (of the last 60 days) and allow us to easily identify flaky unit-tests. [Test page on codecov](https://app.codecov.io/github/servo/servo/tests) based on an uploaded report from a try run. Additionally add a catch-all parameter for `test-unit` which is passed through to the `cargo nextest` invocation, useful for e.g. stressing a test via `--stress-count`. Testing: Manually tested with [try run](https://github.com/servo/servo/actions/runs/18529823800) --------- Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
10 lines
217 B
TOML
10 lines
217 B
TOML
[profile.default]
|
|
# Print a slow warning after period, terminate unit-test after 4x period.
|
|
slow-timeout = { period = "5s", terminate-after = 4 }
|
|
|
|
[profile.ci]
|
|
fail-fast = false
|
|
|
|
[profile.ci.junit]
|
|
path = "junit.xml"
|