Context
The first scheduled mutation-testing run (actions/runs/28850972177) correctly scoped to the Rust files changed on main in the preceding 25 hours, but the unmutated baseline failed (cargo-mutants exit 4), so no mutants were tested:
test hnsw::tests::edge_harvest::build_with_edges_has_consistent_count::case_1 ... FAILED
test result: FAILED. 526 passed; 1 failed; 1 ignored
Analysis
CI's baseline is cargo nextest run (per-test process isolation), while cargo-mutants runs plain cargo test (tests share a process per binary). A test that passes under nextest but fails under cargo test is either flaky or depends on process isolation (global state, environment mutation, statics, working-directory effects).
hnsw::tests::edge_harvest::build_with_edges_has_consistent_count::case_1 should be investigated for shared-state sensitivity (or flakiness) under plain cargo test --all-features. Reproduce with:
cargo test --all-features -p chutoro-core build_with_edges_has_consistent_count
(and, if it passes in isolation, run the whole crate's tests in one process to expose ordering effects).
Impact
Until the test passes under plain cargo test, every scheduled mutation run that detects changed files will fail its baseline and test nothing. The mutation workflow is informational and does not gate PRs, but the signal is currently blocked.
Context
The first scheduled mutation-testing run (actions/runs/28850972177) correctly scoped to the Rust files changed on
mainin the preceding 25 hours, but the unmutated baseline failed (cargo-mutants exit 4), so no mutants were tested:Analysis
CI's baseline is
cargo nextest run(per-test process isolation), while cargo-mutants runs plaincargo test(tests share a process per binary). A test that passes under nextest but fails undercargo testis either flaky or depends on process isolation (global state, environment mutation, statics, working-directory effects).hnsw::tests::edge_harvest::build_with_edges_has_consistent_count::case_1should be investigated for shared-state sensitivity (or flakiness) under plaincargo test --all-features. Reproduce with:cargo test --all-features -p chutoro-core build_with_edges_has_consistent_count(and, if it passes in isolation, run the whole crate's tests in one process to expose ordering effects).
Impact
Until the test passes under plain
cargo test, every scheduled mutation run that detects changed files will fail its baseline and test nothing. The mutation workflow is informational and does not gate PRs, but the signal is currently blocked.