From b77f19626d31f34931813b49cb4dfdb19026576a Mon Sep 17 00:00:00 2001 From: Martin Pool Date: Sat, 20 Jul 2024 06:37:30 -0700 Subject: [PATCH] Fix up NEWS --- NEWS.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/NEWS.md b/NEWS.md index d02f5d46..fdf43151 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,8 +1,6 @@ # cargo-mutants changelog -## 24.7.0 - -- Fixed: The auto-set timeout for building mutants is now 2 times the baseline build time times the number of jobs, with a minimum of 20 seconds. This was changed because builds of mutants contend with each other for access to CPUs and may be slower than the baseline build. +## Unreleased - Changed: No build timeouts by default. Previously, cargo-mutants set a default build timeout based on the baseline build, but experience showed that this would sometimes make builds flaky, because build times can be quite variable. If mutants cause builds to hang, then you can still set a timeout using `--build-timeout` or `--build-timeout-multiplier`. @@ -10,6 +8,10 @@ - Changed: cargo-mutants no longer passes `--cap-lints=allow` to rustc. This was previously done so that mutants would not unnecessarily be unviable due to triggering compiler warnings in trees configured to deny some lints, but it had the undesirable effect of disabling rustc's detection of long running const evaluations. If your tree treats some lints as errors then the previous behavior can be restored with `--cap-lints=true` (or the equivalent config option), or you can use `cfg_attr` and a feature flag to accept those warnings when testing under cargo-mutants. +## 24.7.0 + +- Fixed: The auto-set timeout for building mutants is now 2 times the baseline build time times the number of jobs, with a minimum of 20 seconds. This was changed because builds of mutants contend with each other for access to CPUs and may be slower than the baseline build. + ## 24.5.0 - Fixed: Follow `path` attributes on `mod` statements.