Clippy Keeps Tests on the Kit
Each workspace's clippy.toml refuses, in every crate and its tests,
the raw calls the kit replaces: std::thread::sleep,
tokio::time::sleep and std::process::Command::new. A call that
stays says why where it is:
#[expect(clippy::disallowed_methods, reason = "a fake model slow on purpose")]What Clippy can't see
A pattern of calls, not one call, is read from the source by a repository check: a skip printed by hand, a port probed free and let go, an assertion on elapsed time, a wait made of a loop that sleeps, a test's change to its own process's environment, a child's environment cleared with no runtime folder given, and the folders and programs a test makes by hand (the check). A raw call that stays says why; one that says it "moves onto the testing kit" is counted, and the count only goes down.
Starting a program
Link's own code starts a program from
link_secretive::process::command, and a test's from
env::command.