3 Commits

Author SHA1 Message Date
Simon Sapin
894327e5d9 Don’t print passing unit tests (#43902)
This removes from the output of `./mach test-unit` hundreds of lines
like:

```
        PASS [   0.011s] style_tests str::test_str_join_empty
```

Signed-off-by: Simon Sapin <simon@igalia.com>
2026-04-04 01:59:05 +00:00
Jonathan Schwender
eca996ada3 Upload junit report of unit-tests in CI (#39897)
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>
2025-11-17 15:07:56 +00:00
Jonathan Schwender
8ec1e6e731 ci: Use nextest --retries in CI (#39817)
Follow-up to #39812, using nextests builtin retry feature to rerun flaky
unit-tests.
This also adds a per-test timeout, replacing the global timeout set for
the retry action. We could also add a global timeout for nextest tests,
but per-test timeouts should be sufficient and noticably speedup CI when
individual unit tests get stuck.

Testing: [mach
try](https://github.com/servo/servo/actions/runs/18519094535) running
the unit-tests with retries in CI.

---------

Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
2025-10-15 08:59:15 +00:00