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
{{ message }}
Repository navigation
Fork CI re-run: leftover minors from #707 reviews #709
Leftover minor points from the round-2 reviews of #707 (automatic re-run of fork CI after known infrastructure failures, #130). None blocks; each fails closed today or is rare.
A pass that stops while opening the tracking issue (issue created, reply lost) can leave two tracking issues on the next pass.
The "memory full" box can be a slice several jobs share, so another job's OOM kill can count for this one.
If GitHub's annotation cap drops the real memory note, a fake one printed by a step could count.
A start probe step that stalls skips the job's tests and turns it red.
A person's re-run of a run older than 6 h is never looked at.
The runbook claims "each rule line pinned"; a few time-limit and stall lines still have no test.
The Fix comment's "nothing reads .git/config" is wrong: the sync check's git ls-remote runs in the checkout and sends the token (only to github.com, so harmless).
Activity
fork-ci-rerun runbook: formatter layout
fork-ci-rerun: no note after a stopped end probe; review minors
fork-ci-rerun: close the leftover minors from the #707 reviews (#721)
fork-ci-rerun: close the leftover minors from the #707 reviews (#721)
fork-ci-rerun: close the leftover minors from the #707 reviews (#721)
fork-ci-rerun: close the leftover minors from the #707 reviews (#721)