You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci(matrix): nothing asserted that a host the table names was actually scanned
Every check in this workflow is per host, and no per-host check can notice a host
that never ran. Deleting a host from the matrix silently retires every
expectation the table holds for it: nothing measures those rows, nothing compares
them, and the workflow is green.
The new `coverage` job reads the expected table as a whole and requires the run
to have covered it — both directions. A host with rows and no scan is named; a
host that scanned and has no rows is named as a new build host nobody declared
expectations for, which is a cause rather than 40 unexplained cells.
⭐ And it ties the axis to the release. The set of build hosts is DERIVED from
`release.yml`'s asset names rather than restated, so adding a fifth published
host fails this step until the matrix covers it. A host that gets a binary and no
scan is a host whose target table is a claim nobody checked; a host scanned and
never shipped is coverage spent on a machine no user has.
⚠️ It reds right now, by design: the release publishes four and expected.tsv
holds one. The other three backfill from their first scan artifact.
0 commit comments