mesh-delivery

testdata/captured

Capture the fetch-with-base fixtures from mesh-catalog's code, and prove the checker whole against a real bus with fake build modules (issues 1679, 1287, 1288, 1289, 1678)

2026-10-21 21:23:22 +02:00

beside.go

Judge a head merged onto its trunk through the build modules: run only packages without a kept verdict, the change's own tests first, stop at the first failure (issues 1679, 1288, 1289)

2026-10-21 21:11:43 +02:00

builds.go

The checker's line says whether each candidate module's build is built, failed or waiting, read from the builder's keys (issue 1684)

2026-10-21 21:29:13 +02:00

case.go

Add the checker module: it watches the candidates, claims a verdict once, owes the status mesh/check and ends a check past its bound (issue 1678)

2026-10-21 21:07:14 +02:00

checker_test.go

Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)

2026-10-21 21:20:42 +02:00

checker.go

Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)

2026-10-21 21:20:42 +02:00

doc.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

examiner_test.go

The checker's line says whether each candidate module's build is built, failed or waiting, read from the builder's keys (issue 1684)

2026-10-21 21:29:13 +02:00

fakes_test.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

hold_test.go

Start no check while a delivery builds: the checker reads the controller's bucket of the plans in their build phase, absent as empty (issue 1685)

2026-10-21 21:26:46 +02:00

hold.go

Start no check while a delivery builds: the checker reads the controller's bucket of the plans in their build phase, absent as empty (issue 1685)

2026-10-21 21:26:46 +02:00

judge.go

The checker's line says whether each candidate module's build is built, failed or waiting, read from the builder's keys (issue 1684)

2026-10-21 21:29:13 +02:00

kept_test.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

kept.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

line_test.go

Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)

2026-10-21 21:20:42 +02:00

line.go

Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)

2026-10-21 21:20:42 +02:00

preview.go

Write a preview of the conflicts for a head that does not merge, and give the candidate's modules the reason; pin mesh-sdk to the R4c-5a head (issue 1445)

2026-10-21 21:25:45 +02:00

results.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

store.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00