running 1 test
test clock::exhaustion_tests::failed_constructor_returns_exclusive_backend_after_partial_write ... FAILED

failures:

failures:
    clock::exhaustion_tests::failed_constructor_returns_exclusive_backend_after_partial_write

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 5 filtered out; finished in 0.00s

   Compiling turkos-os-clock v0.1.0 (<project>/reports/os-implementation/K941-K959-preparation-T8L8pi/mutant-failed-constructor-admitted/os-clock)
warning: variable does not need to be mutable
   --> src/clock.rs:194:16
    |
194 |     pub fn new(mut backend: B) -> Result<Self, (Error, B)> {
    |                ----^^^^^^^
    |                |
    |                help: remove this `mut`
    |
    = note: `#[warn(unused_mut)]` (part of `#[warn(unused)]`) on by default

warning: `turkos-os-clock` (lib test) generated 1 warning (run `cargo fix --lib -p turkos-os-clock --tests` to apply 1 suggestion)
    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.21s
     Running unittests src/lib.rs (reports/os-implementation/K941-K959-preparation-T8L8pi/mutant-failed-constructor-admitted/target/debug/build/turkos-os-clock/a3ef14b6317177d5/out/turkos_os_clock-a3ef14b6317177d5)

thread 'clock::exhaustion_tests::failed_constructor_returns_exclusive_backend_after_partial_write' (41400147) panicked at src/clock.rs:632:22:
failed constructor
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: test failed, to rerun pass `--lib`