From 661fb8a74227377bfbd58c5a63cb896dcd616818 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 10:33:22 +0100 Subject: [PATCH] Design 47 G: name the runs' asks where they are known, bound the runs, time every reader The lead's answers A-466m to A-466o: the assigner names the composition runs' asks in its step-progress, each run's bound is a setting, and since the watchman on main times only a build seat's running ask, it now times every pipeline step that reads a run, so a reader no part ends is said as pipeline-stands. --- .../47-delivery-from-commit-to-delivered.md | 5 ++- .../47-milestones/G-22-lead-answers-2.md | 8 ++++ .../G-24-composition-runs-and-test-runs.md | 38 +++++++++++++++---- 03-DESIGN/01-to-be/47-milestones/G.md | 2 +- 4 files changed, 43 insertions(+), 10 deletions(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index d6a552c7..54f455ff 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -1981,14 +1981,15 @@ ADR 0667's checks, of milestone G itself: the readers, and a reader-only account calling one is refused (whole, assigner and the node-engine's composer, mesh-delivery and `mesh-host`). Live: in the first publish after G's delivery, the composition run asks of a revision number at most its machines, read with `assigner_compositions` and `assigner_inputs`. -109. **One test run per level and tested packages** (design 47 G §724 to §731). A module whose program and tools +109. **One test run per level and tested packages** (design 47 G §724 to §732). A module whose program and tools bundle test one directory runs its unit and integration tests once per level, both artifacts' pipeline steps ending with that result and naming it in `shared`, a failing test failing once, and `pipeline-ended` counting the module's tests once. A rerun that passes moves both artifacts' steps and the pipeline ends again; a runner restarted during a run takes it up again; a replaced reader leaves the ask to the others; at the cap a step ends `could not run` naming the fill; a second revision with the same digests runs a failed test again (whole, runner and Go build module, mesh-delivery and mesh-catalog). Live: each module's test steps run once per level, read with - `runner_test_runs`. + `runner_test_runs`. A reader no part ends raises `pipeline-stands` within five minutes of its last sign of life + (whole, watchman; design 47 G §732). ## What retires diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 492e371b..2a119547 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1573,3 +1573,11 @@ the principle that settles it, cited as "design 47 G A-n". run` by A-466b's bound. - **A-466l** (§718; principle 3) A composition run's request carries the node's `compose-candidate` answer of the moment it started, so a later step of the same candidate reuses that verdict knowingly, within the candidate. +- **A-466m** (§729; principle 1) The runs' asks are named in `mesh-wants`' `step-progress`, and the watchman times a + composition step from there: the runner says `step-started` before any run is chosen, so the part that knows says it. +- **A-466n** (§720, §725; principle 11) A run's bound is a setting: the assigner's `composition-step-bound`, default 30 + minutes (the step bound of 2026-10-26), and the runner's `test-step-bound` per level, its default that level's + existing run bound. +- **A-466o** (§730, §732; principle 3) After a return to an earlier build, the watchman's `pipeline-stands` says a + reader left standing; the watchman on main timed only a build seat's running ask, so §732 makes it time every step + that reads a run. diff --git a/03-DESIGN/01-to-be/47-milestones/G-24-composition-runs-and-test-runs.md b/03-DESIGN/01-to-be/47-milestones/G-24-composition-runs-and-test-runs.md index ae0c3fbf..694b8451 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-24-composition-runs-and-test-runs.md +++ b/03-DESIGN/01-to-be/47-milestones/G-24-composition-runs-and-test-runs.md @@ -8,6 +8,7 @@ decisions: - "ADR 0667" - "ADR 0666" - "ADR 0596" + - "ADR 0564" - "ADR 0267" --- @@ -16,7 +17,7 @@ decisions: One file of milestone G's part of [design 47](../47-delivery-from-commit-to-delivered.md); the part opens at [G.md](G.md). Its design lines are numbered across every file of the part and cited as "design 47 G §n". -*§718 to §731 come from milestone G's live delivery of 2026-11-17. The 24 pipelines of one catalog revision asked 96 +*§718 to §732 come from milestone G's live delivery of 2026-11-17. The 24 pipelines of one catalog revision asked 96 composition runs, one per pipeline and machine, and 80 more when they were asked again. Each run kept its own copy of a node's input of 1.1 to 1.5 MB in the assigner's state `inputs`, which reached its 64 MiB cap twice. The indexer's and the teller's same failing tests failed once per artifact. The operator, 2026-11-17 about 10:20 CET: "In G, now". @@ -65,9 +66,10 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci - **`could not run` is never read.** A step that finds an ended run whose outcome is `could not run` starts a new run, replacing the key by compare-and-set; its former readers have already ended `could not run` with it. - **The bound.** A run whose `ask` has no `step-ended` within the bound of the step that started it (the step's own - bound key with its time to live, A-77, A-101) ends `could not run`, naming the ask and the bound, and every reader + bound key with its time to live, A-77, A-101; A-466n) ends `could not run`, naming the ask and the bound, and every reader with it. The end is heard on the assigner's durable consumer of the build seat's `step-ended` (A-240); the assigner - never reads the build seat's state (ADR 0596). + never reads the build seat's state (ADR 0596). A composition step's bound is the assigner's setting + `composition-step-bound`, default 30 minutes (the step bound of 2026-10-26). - §721 **A machine's verdict names the modules it blames.** (ADR 0666 §17; A-452, A-466g, A-466h; principles 10, 3, 7 and 11) The composer's verdict of a machine (mesh-delivery-sdk's `composer.Machine`, answered by the node-engine's `mesh-compose`) gains `blamed`, a list of `{module, problem}`. @@ -140,7 +142,8 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci The runner hears the run's end as the build seat's `step-ended` of its `ask`, on its durable consumer, as it hears every step (§24). A run whose `ask` has no `step-ended` within the bound of the step that asked it ends `could not - run`, as §720 has it, and every reader with it. At its start the runner takes up again each key with no `ended`, by its + run`, as §720 has it (A-466n), and every reader with it. A test step's bound is the runner's setting + `test-step-bound`, one per level, its default its level's existing run bound. At its start the runner takes up again each key with no `ended`, by its `ask` and that bound. It deletes a key once the time its setting `test-runs-kept`, default 7 days, names has passed since its `ended`, in the step log's order as §330 ages its `pipelines`, and deletes the run's output object with the key, after the last reader's end. At the cap no run is asked, and the step ends `could not run`, naming the fill, as @@ -193,13 +196,31 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci A step that names `shared` names its own build-input fingerprint beside it, as every `step-ended` does (§73). A composition step's `step-started` is said by the runner when it asks the assigner, before any run is chosen, so it - cannot name the runs' asks; the assigner's `step-progress` carries them instead, and the watchman times a composition - step from that (§496, A-262). + cannot name the runs' asks; the assigner, the part that knows them, names them in its `step-progress`, and the + watchman times a composition step from that (§496, A-262, A-466m). - §730 **What runs in flight, and going back.** (§65, §78; ADR 0666 §19, §24; ADR 0667 §9; A-466k; principle 3) A composition step or test step asked before the new assigner or the new runner runs ends by the path it was asked under, one run per step; composition runs and test runs are made only for steps asked after the new part runs. A return to an earlier build (§78) leaves `composition-runs` and `test-runs` unread; their readers are ended `could not - run` by the bound of §720 and §725. + run` by the bound of §720 and §725 once the new build runs again. Until then the earlier build applies no such bound, + and a reader standing still is said by the watchman as `pipeline-stands`, by §732 (A-466o). +- §732 **The watchman times every step that reads a run.** (§75, §496, §602; ADR 0564 §2, §4; ADR 0666 §24; A-466o; + principles 3 and 1) §75 and §496 time each pipeline step from its `step-started` or its latest `step-progress`, but + the watchman on main times only a build seat's running ask (its `ask-taken` and `step-progress`) and a step queued + for a build node; a step whose run has ended, or a composition step waiting on the assigner, is timed by nothing. + From G the watchman also: + - **hears** the runner's `step-started` and `step-ended` of every pipeline step (it consumes them already, for the + build capacity), and `mesh-wants`' `step-progress`, a `consumes` entry its manifest gains; + - **keeps** each started step with no `step-ended` in memory under `/`, its clock begun at its + `step-started` and begun again at each `step-progress` whose `ask` is the step's own ask (§496) or an ask its + `shared` names (§729), and at the `step-ended` of the run's ask a test step names; + - **raises** `pipeline-stands` for that step when its clock passes the watchman's existing five-minute progress bound + (§75), naming the pipeline, the step and the ask it last heard of, and clears it at the step's `step-ended`. A + step said waiting on a person, or queued for a build node (§86), is owed no progress, as today; + - **seeds** its open steps at its start from the runner's `stands`, as §75 has it. + + So a reader that neither the assigner nor the runner ends, after a return to an earlier build or any fault, is said + within five minutes of its last sign of life. - §731 **How it is checked.** Tests 108 and 109. - **Whole (assigner, mesh-delivery), test 108.** Two composition steps of one candidate started at once make one key, one request and one run ask. Three composition steps of one revision on two machines start two runs, and each step @@ -221,6 +242,9 @@ domain of 2026-11-17 was answered by the lead in A-466 to A-466l (G-22), each ci leaves the ask to the other readers. At the cap a step ends `could not run`, naming the fill. A second revision with the same digests runs a failed test again. `runner_test_runs_drop` deletes the key and its output object, and a reader-only account calling it is refused. + - **Whole (watchman), tests 108 and 109.** A composition step whose `mesh-wants` `step-progress` stops raises + `pipeline-stands` within five minutes; a test step whose run's ask ended with no `step-ended` of the step raises it + five minutes later; each clears at the step's `step-ended`; a step waiting on a person raises nothing. - **Live.** In the first publish after G's delivery, the composition run asks of each revision number at most its machines, read with `assigner_compositions` and `assigner_inputs`; each module's test steps run once per level, read with `runner_test_runs`. diff --git a/03-DESIGN/01-to-be/47-milestones/G.md b/03-DESIGN/01-to-be/47-milestones/G.md index 46b6ac82..9b39c64e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G.md +++ b/03-DESIGN/01-to-be/47-milestones/G.md @@ -113,6 +113,6 @@ The part is twenty-four files, each read whole, its design lines numbered across - [G-21-provider-and-revert-ask](G-21-provider-and-revert-ask.md): the provider a requirement points to, the named seat and the contribution edge (§708, §709, completing §357), and the assigner's ask of a held revert (§710, completing §300), the edge an acting rule gives (§711, completing §47's kind 5), the validation before take-in (§712, §713, completing §16), the take-in and groups of every watched branch (§714, §715), where the gate keeps a group's members (§716) and the seats of the status view's and the assigner's views, followed before their holder is known (§717). - [G-22-lead-answers-2](G-22-lead-answers-2.md): the lead's answers continued, from A-182. - [G-23-after-delivery](G-23-after-delivery.md): what is owed once G is delivered. -- [G-24-composition-runs-and-test-runs](G-24-composition-runs-and-test-runs.md): one composition run per candidate and machine, one test run per level and tested packages, from G's live delivery of 2026-11-17 (§718 to §731). +- [G-24-composition-runs-and-test-runs](G-24-composition-runs-and-test-runs.md): one composition run per candidate and machine, one test run per level and tested packages, from G's live delivery of 2026-11-17 (§718 to §732). Design 34's milestone [every-event](../34-milestones/every-event.md) and design 46's milestone [7-approval-mark](../46-milestones/7-approval-mark.md) ship in milestone G's release, built in its repositories beside G's lines (lead-47, 2026-11-11 15:30 CET); where one of their lines and a line of G differ, G's later line holds and the other is corrected in place (§624 to §626).