From 5f1fa6c297cf1136ad90b15d9c7a20cd302f64b0 Mon Sep 17 00:00:00 2001 From: Eliah Kagan Date: Wed, 27 Nov 2024 21:06:46 -0500 Subject: [PATCH] Bring back `--no-tests=warn` when needed `justfile` This was temporarily removed to verify that we no longer need to set `NEXTEST_NO_TESTS` to `fail` explicitly in `ci.yml` to get that failing behavior, now that it is implied starting in `cargo-nextest` version 0.9.85. It is now brought back, so that we do not get that error in the one place where we know there are no test cases yet do tell `nextest` to run tests. --- justfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/justfile b/justfile index c82db16edf8..6323a0670da 100755 --- a/justfile +++ b/justfile @@ -186,7 +186,7 @@ unit-tests: cargo nextest run -p gix --no-default-features --features basic,extras,comfort,need-more-recent-msrv cargo nextest run -p gix --features async-network-client cargo nextest run -p gix --features blocking-network-client - cargo nextest run -p gitoxide-core --lib + cargo nextest run -p gitoxide-core --lib --no-tests=warn # These tests aren't run by default as they are flaky (even locally) unit-tests-flaky: