Design 47 H: section 10, finding 165
This commit is contained in:
@@ -681,3 +681,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| The large pipeline of the SDK's release (853 steps, row 159) ended failed at 18:37: the private network module's unit and integration tests failed, and every other mover passed; its movers get no pipeline by themselves (row 147's rule) and will ride the next merge that touches them. The review of the publish-queue change (rows 158 and 160) found one thing: its read tool reads the builder's own states in pages, which H-A-255 forbade for H1 because each page replays the bucket; H-A-292 allows it for a module's own tool when one page of about 768 KB holds the whole state (one replay instead of a request per key), and the review judges the same head again (rows 158, 159 and 160); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Owed: a failed pipeline's movers put in a pipeline again. | H1 (the review); H2 (the re-pipelining) |
|
||||
| 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) |
|
||||
|
||||
Reference in New Issue
Block a user