Documentation
¶
Overview ¶
Command covratchet judges one `go tool cover -func` profile against a per-lane record of the functions already known to be below 100%.
It replaces a gate on the ROUNDED total, which could not be calibrated. On main both POSIX lanes report `coverage: 100.0%` and pass while printing 19 (ubuntu) and 16 (macOS) functions below 100%, the lowest at 75.0%. The tolerance is whatever %.1f absorbs at the current repository size: nobody chose it, nothing states it, and it SHRINKS as the codebase grows. A function falling from 100% to 75% is free until it is suddenly fatal, and the commit that trips the gate is not the one that created the debt.
It was also arbitrary which lane you believed. On PR #727 the same commit gave 99.9% on ubuntu (FAIL) and 100.0% on macOS (pass): ubuntu carried three filesystem-dependent functions macOS does not, so one further dead function tipped only one lane over the edge.
So: the gate is the SET of below-100 functions, recorded per lane, and it may not grow. Percentages are reported but not gated -- coverage is measured under -race, where a percentage jitters while the set does not, and a gate that flakes is a gate people learn to rerun.
Source Files