Noticed while confirming main was green for the v4.4.0 release (#276). Not
blocking that release — a cleanup: PR.
.github/workflows/CI.yml:22 and :78 both set fail-fast: false. AGENTS.md §4
step 10 asks the matrix to stop at the first failing job, so an answer comes back
sooner and the remaining runners are left for other work; the box's local mirror
is already set that way.
The tradeoff is worth stating rather than assuming: with fail-fast: true a
failure on one cell cancels the others, so you lose the "is this Windows-only or
everywhere?" signal in the same run and have to re-run to get it. On a matrix
this wide (Julia 1.11/1.12 × ubuntu/windows/macOS, plus coverage jobs) that
signal is worth something. Whoever picks this up should decide which of the two
costs more here.
Noticed while confirming main was green for the v4.4.0 release (#276). Not
blocking that release — a
cleanup:PR..github/workflows/CI.yml:22and:78both setfail-fast: false. AGENTS.md §4step 10 asks the matrix to stop at the first failing job, so an answer comes back
sooner and the remaining runners are left for other work; the box's local mirror
is already set that way.
The tradeoff is worth stating rather than assuming: with
fail-fast: trueafailure on one cell cancels the others, so you lose the "is this Windows-only or
everywhere?" signal in the same run and have to re-run to get it. On a matrix
this wide (Julia 1.11/1.12 × ubuntu/windows/macOS, plus coverage jobs) that
signal is worth something. Whoever picks this up should decide which of the two
costs more here.