Integration tests that R4g never ran now pass: the assigner's fixture, the builder's restart test, four checker tests (issues 1927, 1928, 1929) #28

2026-10-23T21:22:47Z

mesh-tools commented

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

R4g merged by hand before any check ran (issue 1925 refused every check), so mesh-delivery's main fails its integration level. Test-only, no production change:

1927 (a31bd7d4): the assigner's TestAChangeIsComposedOnTheBus builds its candidate with delivery.FingerprintSet (as the indexer does in production), which the SDK requires.
1928 (b303e32a): the builder's TestARestartedBuilderPutsNoSecondAsk closes the fake nodes before the pullers start (a pull in hand took the first ask), waits on state with a failing deadline, no fixed sleep.
1929 (cd3e55e0): four checker tests follow what R4g decided — a modules key so only the Go build module judges (1887 A12), the fake echoes the fetch's beside (besideFor), the stale-pin test drops 'no test ran' (ADR 0525 §3), kept is readable (1887 A5b).

Proof: local runs of all eight modules' integration levels green (the operator's guideline after a failed try); try-1792790294797477664 passed (19 integration run, 521 kept), try-1792790490356418699 passed (all kept).

Moves nothing that runs (tests only). Unblocks the checks of 1923 and 1901's mesh-delivery half.

Reviewed-by: review-1927@shanks at cd3e55e056
Pushed-by: fix-1923@shanks

R4g merged by hand before any check ran (issue 1925 refused every check), so mesh-delivery's main fails its integration level. Test-only, no production change: - **1927** (a31bd7d4): the assigner's TestAChangeIsComposedOnTheBus builds its candidate with `delivery.FingerprintSet` (as the indexer does in production), which the SDK requires. - **1928** (b303e32a): the builder's TestARestartedBuilderPutsNoSecondAsk closes the fake nodes before the pullers start (a pull in hand took the first ask), waits on state with a failing deadline, no fixed sleep. - **1929** (cd3e55e0): four checker tests follow what R4g decided — a modules key so only the Go build module judges (1887 A12), the fake echoes the fetch's beside (besideFor), the stale-pin test drops 'no test ran' (ADR 0525 §3), kept is readable (1887 A5b). Proof: local runs of all eight modules' integration levels green (the operator's guideline after a failed try); try-1792790294797477664 passed (19 integration run, 521 kept), try-1792790490356418699 passed (all kept). Moves nothing that runs (tests only). Unblocks the checks of 1923 and 1901's mesh-delivery half. Reviewed-by: review-1927@shanks at cd3e55e056051093fce863883c1d91bbdf47d313 Pushed-by: fix-1923@shanks

mesh-tools added 3 commits 2026-10-23 21:22:47 +00:00

Give the assigner test's candidate the SDK's fingerprint set, which the SDK refuses without (issue 1927) a31bd7d4a5

Close the builder test's nodes from the bed's start, so no pull in hand takes the first ask (issue 1928) b303e32a41

Bring the checker's integration tests to what R4g decided: Go-only repository, echoed beside, readable kept (issue 1929)

mesh/delivery delivered

Details

mesh/check pass cd3e55e05605 on fae4d48e09a5 | unit 0 run 483 kept | int 0 run 540 kept | clone 17s | composition passed on 3 machines

cd3e55e056

mesh-tools commented

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

Delivery novox/mesh-delivery@cd3e55e05605 — delivered since 2026-10-23T21:26:23Z

Delivery plan — builds mesh-delivery-assigner, mesh-delivery-builder, mesh-delivery-checker → ace, novox, shanks; no bus step

tier 0: mesh-delivery-assigner, mesh-delivery-builder, mesh-delivery-checker
ace: receives mesh-delivery-assigner
novox: receives mesh-delivery-checker
shanks: receives mesh-delivery-builder
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-assigner, mesh-delivery-builder is judged on its first machine

Machines

mesh-delivery-assigner on every machine running it: sent
mesh-delivery-builder on every machine running it: sent
mesh-delivery-checker on every machine running it: sent

Transitions

2026-10-23 21:22 (new) → proposed (announced): novox/mesh-delivery#28's head announced
2026-10-23 21:23 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 21:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 21:24 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-23 21:24 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-23 21:26 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-delivery@cd3e55e05605` — **delivered** since 2026-10-23T21:26:23Z **Delivery plan** — builds mesh-delivery-assigner, mesh-delivery-builder, mesh-delivery-checker → ace, novox, shanks; no bus step - tier 0: mesh-delivery-assigner, mesh-delivery-builder, mesh-delivery-checker - ace: receives mesh-delivery-assigner - novox: receives mesh-delivery-checker - shanks: receives mesh-delivery-builder - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-assigner, mesh-delivery-builder is judged on its first machine **Machines** - mesh-delivery-assigner on every machine running it: sent - mesh-delivery-builder on every machine running it: sent - mesh-delivery-checker on every machine running it: sent **Transitions** - 2026-10-23 21:22 (new) → proposed (announced): novox/mesh-delivery#28's head announced - 2026-10-23 21:23 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-23 21:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-23 21:24 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-23 21:24 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-23 21:26 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 263ff54a4e into main

2026-10-23 21:24:33 +00:00

mesh-tools deleted branch fix/1927-assigner-fpset

2026-10-23 21:24:33 +00:00

mesh-tools referenced this pull request

2026-10-23 21:30:10 +00:00

The indexer keeps an unreadable manifest's inputs, so an SDK upgrade judges it again at start (issue 1923) #29

mesh-tools referenced this pull request

2026-10-23 21:30:18 +00:00

The checker keeps a failed test's whole message with its cause first, and its status names the cause (issue 1901, with mesh-catalog) #30

Sign in to join this conversation.