Skip to main content

baseline_blocked_run_error

Function baseline_blocked_run_error 

Source
pub fn baseline_blocked_run_error(
    report: &MutationReport,
) -> Option<ProgrammaticError>
Expand description

The error of a run in which no mutant got a test result while tests failed with no active mutant.

A mutant has a test result when it is killed, timeout, survived or flaky. Such a run measured nothing, because the failed tests could not detect a mutant. The error fires only when each other mutant is final (no_coverage, runtime_error, compile_error, equivalent or pruned). A pending mutant means that the time budget or --max-mutants stopped the run, so the baseline failure is not the cause. A run without a baseline failure and with only no_coverage mutants is a fact about the tests and gets no error. The error has exit code 2 and the code FALLOW_MUTATION_BASELINE_FAILED, the same as a dry run that fails outside each test file. It names the first failure and the first line of its message.