Created Started Cancelled
By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Reproduce a timed-out control counting as a failed control A control mutation is a no-op, so a suite that kills one is unsound and the run should fail. A suite that merely runs past its timeout tells us nothing of the sort: the run did not finish inside its budget, which is a fact about the budget and the machine rather than about whether the harness reports a non-diff as a survivor. The driver conflates the two, so a loaded machine fails the run with "mutation testing may be unsound" while nothing survived. The test here has a control whose suite only sleeps past its timeout and asserts it is not counted as a failed control. This test fails: the tally reads 1.