Next gen: never run the same test twice, anywhere (passes as portable signed proofs) issue #296 open andymccall opened this 11 days ago · 3 comments

First slice landed on main (not yet deployed): a fork starts green where upstream proved the same state. A push's job with no pass of its own on that state reuses one from the repositories it was forked from, nearest first, up to five up, only from an upstream that is public or has the fork's owner. The run page and the check say whose pass it was and link to it.

Next slices, in order:

• Any repository on the hub, not only the fork line: a pass is keyed by state, job spec and sandbox, so mirrors and Diffusion consumers holding the same state could reuse it too (same visibility rule).
• Verify before reusing: check the receipt's signature against the runner's bound key, and its transparency-log inclusion, and run again when either fails, so nothing is taken on trust.
• Test-level reuse with Flow's coverage: a change that touches no test's inputs reuses that test's last pass.

Slices 2 and 3 on main (not yet deployed): a push's job with no pass of its own reuses one from any repository on the hub holding the same state (public, or the same owner), after the fork line; and another repository's pass stands only on its runner's signed receipt, kept when the job finished and checked again from that repository's store (verifies, key not revoked), else the job runs here. Only passes that ran in the repository offering them are taken. Left: test-level reuse with Flow's coverage.

Reopened: a commit message saying "closes issue #296's C2" closed it by mistake; test-level reuse is still to do.