Shrink the Failing Input Before a Flake Freeze Can Be Written
A flake freeze is a quarantine row, not a pardon. Write one only after a property failure shrinks to a minimal fixture, a fixed replay set splits into completed assert outcomes, and the record stores seed, fixture digest, runner id, and expiry. A timeout is an infrastructure result. It does not enter the freeze ledger. CI logs collapse three different failures into one red line. An assertion miss…
A flake freeze is not a pardon for property failures. It occurs only after a failure is reduced to its smallest form, with the record containing essential details like seed, fixture digest, runner ID, and expiry. CI logs condense various failures into a single red line, while an assertion miss indicates a patch-breaking failure on a completed run.
A timeout signals the runner's cessation of waiting, and a harness error means the check did not yield a verdict. These issues require distinct handling because a single flaky bucket can lead reviewers to overlook genuine regressions and runner defects.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
