Design 47 G: one composition run per candidate and machine, one test run per tested packages
G's live delivery of 2026-11-17 composed each machine once per pipeline (96 runs for one revision, 80 more on rerun, the assigner's inputs state at its cap twice) and ran the same tests once per artifact. Pipelines of one candidate now read one composition run per machine, kept by the assigner, whose verdict names the modules it blames so one module's fault fails only its own pipelines; test steps naming the same packages read one test run, kept by the runner. The operator, 2026-11-17 about 10:20 CET: "In G, now".
This commit is contained in:
@@ -620,6 +620,15 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
|
||||
- **composition step** — the pipeline step that composes each machine's declaration with a change, by the composer built
|
||||
from its heads in the sandbox, refusing a change in which two modules own one path; served by the seat `mesh-wants`
|
||||
(ADR 0666 §17). From milestone G's delivery it replaces the **composition check**.
|
||||
- **composition run** — the one run of the composer for one candidate on one machine, started by the first
|
||||
composition step of that candidate that needs the machine and kept by the assigner in its state `composition-runs`;
|
||||
every composition step of the candidate whose module is placed on the machine reads its verdict (design 47 G §718).
|
||||
Not a **composition**, one module's resources composed for one node; nor the **composition step**, the pipeline
|
||||
step that reads one composition run per machine.
|
||||
- **test run** — the one run of a lint, unit test or integration test pipeline step for one level and one set of
|
||||
tested packages at their digests, kept by the runner in its state `test-runs`; every artifact's pipeline step naming
|
||||
the same packages reads its result (design 47 G §724). Not a **pipeline step**, each artifact's own, nor a **run
|
||||
on request**, a whole pipeline that delivers nothing.
|
||||
- **merge check** — what a pull request carries before it may merge, judging the merge of its head into a
|
||||
named **trunk commit**, made in a clone of its own on a build node and never pushed (ADR 0323). One status,
|
||||
`mesh/check`, written by the checker: the change's tests, run by the language's build module, and the
|
||||
|
||||
Reference in New Issue
Block a user