Design 47 H: section 10, finding 166
This commit is contained in:
@@ -682,3 +682,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| The builder's publish-queue change (rows 158, 160 and 162) was approved at its third and last review round: the second round had found the read tool paging on past one page, and the retire rule crossing version series (a standing 0.2 would have retired a done 0.1.x build); H-A-293 settled both (a one-page read past its page answers the first page and says it is capped, with the state's size; the newest reservation and release are found per module and series), and the fix was judged in one commit. Merged at 19:00 (19:00:35, rebased first onto the fix that ends an empty pipeline, the builder's code unchanged) into a pipeline of its own, with its hand pack for the build node (the program and the tools bundle) built beside it, the first of the evening's packs to restart the build node's tool runner (rows 158, 160 and 162); the builder and the runbook. | H1 |
|
||||
| A second re-pin pipeline ended failed at 18:58 on one module's tests, the teller's program and tools integration tests, every other mover passing, after row 162's private network module at 18:37. The movers of these pipelines carry only the re-pin to the SDK release with the event hub fix (row 150: pulls of twenty instead of five hundred, in-progress acks), so the kind is read before another pipeline fails on it: whether the tests depend on the old pull size or timing (a regression every module meets), or fail for their own reasons. The tool runner's pipeline is second in line from 18:58 (rows 150 and 162); mesh-sdk, the teller and the private network module. | H1 |
|
||||
| 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) |
|
||||
|
||||
Reference in New Issue
Block a user