Design 47 H: section 10, row 168's time

This commit is contained in:
2026-11-21 19:17:48 +01:00
parent 0672f6e215
commit ae4211ca48
@@ -684,4 +684,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| A third re-pin pipeline ended failed at 19:01 on the zfs module's tools unit test; the read of all three failures (rows 162 and 164) found none of them the SDK's: the teller's test (an ask refused for want of room is asked again) is sensitive to timing and failed five of seven pipeline runs today, four of them before the SDK's change, so its fix starts now under this milestone (the teller is a module of the delivery system); the private network module's three tests read files outside their own module and failed in every pipeline today (a fix for its repository, after the proof); and the zfs module's test has a data race on the peer's id (a fix for the catalog repository, after the proof). The read also met a missing tool: no tool shows a failed step's test output, only its counts and the names of the failing tests, which belongs with the owed keeping of step outputs (row 144). The tool runner's pipeline was placed at 19:03 with 105 steps; its build, lint, unit and integration steps passed, and validate runs (rows 150, 162 and 164); the teller, the private network module, the zfs module and the pipeline runner (`mesh-delivery-pipeline`). | H1 (the teller's test); later (the two others) |
| The publish-queue change (row 163) runs on the build node since 19:03, the program and the tools bundle, the bundle's restart of the build node's tool runner silencing the tools of the mesh MCP server for about a minute (19:05 to 19:06); within three minutes the builder sent two live publishes and said both published, and its read tool answered the queue (empty) with its three standing publish items. Seen at its start: the start pass wrote one line per module no seat can build (about 6,500 lines the journal suppressed), which can hide other lines for a minute, the kind of row 101's burst (rows 158 and 163); the builder. Owed: one summary line for them. | H1 (live); H2 (the summary line) |
| The tool runner's pipeline (row 165) ended failed at 19:09 on the forge module's six integration steps, while the tool runner's own build, tests, validate and composition had passed; a pipeline's wants are written only when it passes, so the tool runner got none, and a failed pipeline's movers get no pipeline by themselves (row 147). It is the fourth re-pin pipeline of the evening sunk by one module's tests (rows 162, 164 and 165), so the lead stops iterating pipelines and fixes the kind under this milestone: the teller's test that is sensitive to timing, the private network module's tests that read files outside their inputs, and the zfs module's test race, each in its repository, while the forge module's six failures are read. The tool runner gets a pipeline of its own at once, by a one-line probe commit in its repository merged as one call (the operator's word of 2026-11-16 on probe merges), built against the latest published SDK release; the one-call merge of the SDK and the tool runner itself was shown at 12:26 (row 136), and this pipeline shows the delivery part of proof 2 (rows 136, 147 and 165); the pipeline runner (`mesh-delivery-pipeline`), the teller, the private network module, the zfs module and the forge module. | H1 |
| The forge module's six failures (row 167) are one test: its whole-seat test over a real bus, added on 2026-11-20, needs the module's npm packages installed, which the Go integration step never has (it fetches the tree without network), so it has never passed in a pipeline and sank every pipeline carrying the forge since, the one of 14:45 (row 143) included; the forge module and the Go build module (`mesh-build-go`). Settled by H-A-294 (a test that needs tooling its step lacks checks its needs first and ends NOT RUN with the reason and where it was proven, the build module's own precedent), in build in the catalog repository. The probe merge of row 167 landed at 19:13 and became a pipeline of one mover, the tool runner, being watched. The first of the four test fixes is built: the private network module's three tests read their facts from copies in the package's own test data, held equal to the originals wherever the repository is whole; the cause was the artifact's declared paths holding only the module's Go directory (rows 143, 165 and 167). Owed: the Go integration level receives a module's npm tree behind a declared need, and a read tool for a run's test output, which answers nothing through the mesh MCP server today. | H1 (the fixes); H2 (the need and the tool) |
| The forge module's six failures (row 167) are one test: its whole-seat test over a real bus, added on 2026-11-20, needs the module's npm packages installed, which the Go integration step never has (it fetches the tree without network), so it has never passed in a pipeline and sank every pipeline carrying the forge since, the one of 15:03 (row 143) included; the forge module and the Go build module (`mesh-build-go`). Settled by H-A-294 (a test that needs tooling its step lacks checks its needs first and ends NOT RUN with the reason and where it was proven, the build module's own precedent), in build in the catalog repository. The probe merge of row 167 landed at 19:13 and became a pipeline of one mover, the tool runner, being watched. The first of the four test fixes is built: the private network module's three tests read their facts from copies in the package's own test data, held equal to the originals wherever the repository is whole; the cause was the artifact's declared paths holding only the module's Go directory (rows 143, 165 and 167). Owed: the Go integration level receives a module's npm tree behind a declared need, and a read tool for a run's test output, which answers nothing through the mesh MCP server today. | H1 (the fixes); H2 (the need and the tool) |