Design 47 H: section 10, finding 158
This commit is contained in:
@@ -674,3 +674,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
|
||||
| While the re-pin fix (row 154) was built, the pipeline carrying the tool runner (row 151) ended at 17:45 could-not-run: its build ask on the build seat had no word from its holder within the silent bound of forty-five minutes (row 118), because the tool runner's build at that pipeline's fingerprint had been withdrawn by the re-pins' newer builds before it could answer; the tool runner then rode the newest re-pin revision's pipeline, nine of them waiting in the queue; the fixed runner, placed on the control-node by hand at about 18:05, keeps it there from now on. The builder meanwhile says the tool runner's release 0.1.55 is queued at the distribution already, while the registry holds nothing of it; the distribution's word is being read (rows 111, 151 and 153); the pipeline runner (`mesh-delivery-pipeline`), the builder and the artifact registry. | H1 |
|
||||
| The re-pin fix (row 154) was placed on the control-node by hand at 18:05, and the pipeline runner started clean; but the pipeline of row 155 still held the slot: every one of its movers had left to newer pipelines and its last open step had ended could-not-run at 17:45, yet it counted as running, with nine pipelines waiting behind it. The lead cancelled it at 18:09, the second pipeline of this kind to hold the slot with nothing left to do (row 112 was the first) (rows 112, 154 and 155); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-288 (a pipeline ends, and the next is placed, the moment nothing of it is open: at the last mover's leave, at the last open step's end in any outcome, and at the runner's start pass), in build in the runner. | H1 |
|
||||
| The cause of row 156's held slot, read from the pipeline runner's code and the control-node's journal: the pipeline did judge its end at 17:45, but never wrote it; the runner computed every mover's widens inside the end's compare-and-set loop (126 movers, each asking the seat mesh-grants and cut after five seconds, about eleven minutes per try) while the pipeline's key kept changing under it, so every write was refused and the reads were made again (212 cuts between 17:45 and 18:05) until the restart, and the start pass judged no ends (rows 112 and 156); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-289 (the reads an end needs are made once before the compare-and-set and shared by every mover and every retry; a retry reads only the key again), beside H-A-288's end pass at the start; in build in the runner. Owed: the five-second cut of the seat mesh-grants's answer itself (rows 69 and 115). | H1 |
|
||||
| The tool runner's release 0.1.55 (queued at 17:47) waited more than forty minutes to publish, not lost but at the back of the builder's publish queue: a state bucket with one key per holder and version, worked one version at a time, oldest first, the whole bucket listed and read again before every send (about 1,900 subjects; the read tool timed out on it), and every start of the builder asks a publish again for every done build without a release, so old versions of many modules ride ahead of the ones a pipeline waits on; the second slow drain in the builder today (row 149 was the first) (rows 149, 152 and 155); the builder. Settled in H1 by H-A-290 (a publish a pipeline's step waits on goes before any asked again at a start; a withdrawn or taken-over build never publishes; one listing per pass and four sends at a time; a send that does not send says why; the read tool answers at any size), in build in the builder. Owed: the publish queue as a work-queue stream per holder, with tools to drop one item or put it first. | H1 (the five parts); H2 (the stream) |
|
||||
|
||||
Reference in New Issue
Block a user