cargo-hauler 0.6.1 → 0.6.2

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.6.2
+
+### Patch Changes
+
+- 10500db: Fold `cargo test` runs that share an identical `--exact` harness flag.
+  
+  `--exact` joins `--test-threads=N`, `--nocapture`, and `--quiet` as a harness flag a `cargo test` composite carries: libtest OR-s its positional filters and applies `--exact` to each, so `cargo test -p a -- x::y --exact` and `cargo test -p b -- z::w --exact` now run as `cargo test -p a -p b --no-fail-fast -- x::y z::w --exact` — the union of packages with the union of filters, the flag once — with the same cross-package name-collision caveat the substring fold already accepts (under `--exact`, only a test of the same full name in another package). `--exact --nocapture`, the single-test shape agents emit, folds the same way. The harness set must still be identical on every participant, so exact and substring matching never mix: a run with `--exact` never joins a composite without it, and vice versa. Everything else holds: the `--test` / `--lib` selection must match, unfiltered runs fold only with unfiltered runs, requests naming the same packages still need the same filters (#53), a participant inherits a composite failure only when it asked for every package and every filter the composite ran and otherwise reruns alone (#87), and `--skip`, `--ignored`, `--include-ignored`, `--list`, `--format`, `--logfile`, or any other harness flag keeps a run out of composites. A composite now splices the followers' filters in behind the leader's own, ahead of its harness flags (`-- f1 f2 --test-threads=4` rather than `-- f1 --test-threads=4 f2`); libtest reads both alike. (#97)
+
 ## 0.6.1
 
 ### Patch Changes

package/README.md

@@ -198,14 +198,20 @@ become `cargo clippy -p a -p b -- -D warnings`, with the trailer once. Under
 whose own units compiled cleanly is still released as done, the rest rerun
 alone. Folded tests share the composite process and output. `cargo test`
 requests fold when their `--test` / `--lib` selection and harness flags match
-— `--test-threads=N`, `--nocapture`, and `--quiet` are the only flags a
-composite carries, and only when every participant asked for the same set.
-Requests naming different packages may also differ in bare name filters:
+— `--test-threads=N`, `--nocapture`, `--quiet`, and `--exact` are the only
+flags a composite carries, and only when every participant asked for the same
+set. Requests naming different packages may also differ in bare name filters:
 `cargo test -p a -- f1` and `cargo test -p b -- f2` become `cargo test -p a -p
 b --no-fail-fast -- f1 f2`, a run over the union of packages with the union of
-filters (a filter for one package may also match test names in another).
+filters (a filter for one package may also match test names in another). The
+same holds under `--exact`, which libtest applies to each filter it OR-s:
+`cargo test -p a -- x::y --exact` and `cargo test -p b -- z::w --exact` become
+`cargo test -p a -p b --no-fail-fast -- x::y z::w --exact`, the flag once, and
+the only cross-package spill is a test of the same full name in the other
+package. Exact and substring never mix: a run with `--exact` never joins a
+composite without it, and vice versa.
 Requests naming the same packages share no compile and still need the same
-filters; unfiltered runs fold only with unfiltered runs; `--exact`, `--skip`,
+filters; unfiltered runs fold only with unfiltered runs; `--skip`,
 `--ignored`, `--include-ignored`, `--list`, `--format`, `--logfile`, or any
 other harness flag keeps a run out of composites. `cargo nextest run`
 requests fold only on an identical filterset. On success every participant