Design 47 G: the lead's answers A-469w..A-470 (caps, settings, waits, bound keys) #672
@@ -1713,3 +1713,18 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
`mesh-wants`; `TestRun`, `TestRunReader` `{pipeline, artifact}` and `TestRunPackage` `{package, digest}` in
|
||||
`mesh-pipeline-runner`. A-469t's list covers `stands` too: `Wait`'s `shared` is a list of `Shared`, one entry for a
|
||||
test step.
|
||||
- **A-469w** (G-24 A1; §719, §725, A-469d; principle 11) The manifest's `max-mib` of `composition-runs` and of
|
||||
`test-runs` is 64, as `inputs`' is, and each cap setting's `maximum` is 64.
|
||||
- **A-469x** (G-24 A1, A4; §719, §720, §725; principle 11) The time settings (`composition-runs-kept`,
|
||||
`composition-step-bound`, `run-untaken-bound`, `test-runs-kept`, `test-step-bound`) are strings holding a Go
|
||||
duration ("24h", "30m"), reaching the process through a resource file as `outside-wait` does; the cap settings and
|
||||
`blame-tries` are whole numbers.
|
||||
- **A-469y** (G-24 A4; A-469b; principles 3 and 7) A composition run's waiting reader is said by one `wait-held` per
|
||||
reader on `mesh-wants`: `step` `pipeline`, `owner` `mesh-wants`, `module` the reader's module, `node` the machine,
|
||||
`on` `build node`, `since` the run's `started`; it ends by `wait-ended` with how `ran` at the ask's `ask-taken`, or
|
||||
`superseded` when the run ends before it is taken.
|
||||
- **A-469z** (G-24 A5, R3; §723, §726; principle 3) When the last reader leaves and the run's ask is dropped, the run's
|
||||
key ends `could not run`, naming "no reader is left", so a later step of the candidate starts a new run; the same
|
||||
holds for a test run.
|
||||
- **A-470** (G-24 A4, R2; A-468b; principle 8) The second bound key of a run is `untaken.<run key>`, beside §720's
|
||||
`bound.<run key>`, in `composition-runs` and in `test-runs`.
|
||||
|
||||
Reference in New Issue
Block a user