Commit Graph
1566 Commits
Author SHA1 Message Date
jschoubben 96dadc6fde Answer A-473: the builder asks the tagged publish of a reserved version when its build ends 2026-11-17 14:58:19 +01:00
jschoubben a622019bd5 Answer A-472a: the cancel's note stays; the read bound and revisions kept are settings 2026-11-17 14:57:52 +01:00
jschoubben 76c92e4c1e Answer A-472: a pipeline's end is said without waiting on another part 2026-11-17 14:49:36 +01:00
jschoubben 68148d886b Answer A-471: a toolchain is agreed by its language version, the patch not counted 2026-11-17 14:47:57 +01:00
jschoubben aa52fa5345 Answer A-470v: the search blames every refused module, not only the first 2026-11-17 13:08:28 +01:00
jschoubben e671d865d3 Answer A-470u: a reader that leaves or is replaced has its wait ended 2026-11-17 13:08:08 +01:00
jschoubben 5edbcdac6c Answer A-470t: the runner's ends carry no message id, so A-470q holds as built 2026-11-17 13:06:02 +01:00
jschoubben c1c7353191 Answer A-470s: only the build seats are judged for a holder at placing 2026-11-17 13:03:55 +01:00
jschoubben cd3428755a Answer A-470q and A-470r: an end said again has its own message id, and a drop ends only the ends owed 2026-11-17 13:03:28 +01:00
jschoubben 42e9484261 Answer A-470p: a run's end comes before every other act of its step-ended 2026-11-17 12:32:55 +01:00
jschoubben 384ceb714d Answer A-470o: an expiry is judged by the key's absence, and a run's end is never held behind a finding 2026-11-17 12:25:15 +01:00
jschoubben 72bc73df27 Answer A-470n: a run's bound names its ask, so a replaced run's late signal ends nothing 2026-11-17 12:24:05 +01:00
jschoubben d71cbe8b49 Answer A-470m: a reader's end is kept in the key, so a take-up tells a passed reader from a late one 2026-11-17 12:16:40 +01:00
jschoubben 93a3e46923 Answer A-470l: a take-up says no end again for a reader that passed 2026-11-17 12:14:43 +01:00
jschoubben c6943ee76f G-23: the causes found on 2026-11-17 for the assigner's long line, the toolchain disagreement and an untaken merge 2026-11-17 12:12:05 +01:00
jschoubben ff60461f5b Answer A-470k: the case carries the revision's none, so the composer can tell a build that can never be made 2026-11-17 11:58:59 +01:00
jschoubben 10d6d75902 Answer A-470j: a module that can never be built is blamed, not a reason to judge no machine 2026-11-17 11:56:06 +01:00
jschoubben e2e464a046 Answer A-470i: a fill names the cap that refuses, answered by the process that holds it 2026-11-17 11:55:24 +01:00
jschoubben 8231fd0acb Answer A-470h: a pipeline failed for a holderless seat asks none of its steps 2026-11-17 11:54:15 +01:00
jschoubben bb99034295 Answer A-470g: no holder fails at once, and a fill is said against the cap that refuses 2026-11-17 11:50:50 +01:00
jschoubben 12a3ef6960 Answer A-470f: the run drops refuse no caller, as every seat verb admits every caller 2026-11-17 11:48:23 +01:00
jschoubben 520e95a10c Answer A-470d and A-470e: a rerun carries every reader with its mark, and a newer run is told by its ask 2026-11-17 11:39:20 +01:00
jschoubben 328e17112e Answer A-470a..A-470c: aging test runs, an untried module never fails, the composer's four readings 2026-11-17 11:24:13 +01:00
jschoubben f62a73d757 Answer A-469w..A-470: the assigner developer's five questions on caps, settings, waits and bound keys 2026-11-17 11:22:06 +01:00
jschoubben 8884fc9ee7 G-23: the faults met on 2026-11-17, so none is lost before G is delivered 2026-11-17 11:17:23 +01:00
jschoubben 2ed3c5d368 Answer A-469v: a drop's answer names the run and the readers it ended apart, so C1 can go on 2026-11-17 11:11:27 +01:00
jschoubben 9bfb8b0211 Answer A-469t and A-469u: one shared form, and the four run verbs' names and answers, so C1 can go on 2026-11-17 11:10:03 +01:00
jschoubben e88cce45dd Answer A-468..A-469s: G-24's 14 design questions and 20 design-meets-code entries, so its develop can start 2026-11-17 11:04:04 +01:00
jschoubben 92f967f542 Answer A-467a: a composition step with no machine judged never passes 2026-11-17 10:47:50 +01:00
jschoubben cbf12d3380 Merge main (A-467) into the shared-runs design 2026-11-17 10:41:23 +01:00
jschoubben 849a4012d6 Design 47 G: read "no holder" from the seat-holders view, not the seat list
The seat list answers definitions alone (§527); the holders are the seat mesh-module-assigner's
view seat-holders, which the runner now consumes (A-466z).
2026-11-17 10:39:47 +01:00
jschoubben 32302e0bd1 Design 47 G: test 109's line in G-24 names the queued run A-466y keeps 2026-11-17 10:38:51 +01:00
jschoubben 017e20504a Design 47 G: read "no holder" from the seat list, never from five minutes in the queue
A test run queued behind the build capacity with its holder present was ended failed for no
holder after five minutes, which is not true; the queue is §86's finding's and the untaken
bound's to time (A-466y).
2026-11-17 10:38:35 +01:00
jschoubben d7321df3e5 Design 47 G: write in round 2 of the review of the composition runs and test runs
A run's bound times owed progress from the ask's taking, a run never taken ends at a bound of
its own, blame-tries travels in the request, the hand order goes, a test run's output lives
with its key, stands names what a reader waits on, and G-24 reads in number order
(A-466p to A-466x).
2026-11-17 10:37:41 +01:00
jschoubben 605e0878a5 Answer A-467: a composition step never passes on a machine it did not judge; seats from the trunk while the revision names none 2026-11-17 10:35:05 +01:00
jschoubben cebac2e791 Design 47 G: count both run bounds from the ask's taking, 30 minutes
A bound counted from the asking would end a run that only waited in the queue as could not
run, which is not true; the queue is the build-capacity finding's to time (A-466n).
2026-11-17 10:33:58 +01:00
jschoubben 661fb8a742 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.
2026-11-17 10:33:22 +01:00
jschoubben 6b7adc5ec2 Design 47 G: write in the review of the composition runs and test runs
The four reviewers by architectural domain found results crossing candidates, a read of a
build seat's state, fixed durations and caps, unstated seat contract fields and a rerun rule
that differed between the two kinds; the lead's answers A-466 to A-466l settle each. The
lines move to a file of their own, G-24, so G-2 stays under its bound. The split of the main
file and G-22 waits until after G, as the operator decided at 10:31 CET.
2026-11-17 10:31:28 +01:00
jschoubben 77318ca60e Design 47 G: a test run asked again moves every step that reads it; two items after G
The coordinator's answers of 2026-11-17: a step left reading a failed result would say what
is no longer true, so a rerun of a test run moves all its readers; the node-engine's
differing input bytes and the split of design 47's main file wait until after G.
2026-11-17 10:25:15 +01:00
jschoubben 31cd62aeec 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".
2026-11-17 10:24:28 +01:00
jschoubben 399ac934f6 Answer A-465b: the inputs key form is the assigner's own; an ask's key holds its time; old keys age out 2026-11-17 09:46:15 +01:00
jschoubben ec6aae9997 Answer A-461c: the node-engine's golden grant is checked against its invokes; after G: no pass waits on a call 2026-11-17 09:39:53 +01:00
jschoubben cb1ce7291f Answer A-465a: a composition input is kept once per content, shared by the asks that use it 2026-11-17 09:38:02 +01:00
jschoubben 0fc357c96b After G: say catalog, the glossary's word 2026-11-17 09:22:54 +01:00
jschoubben d84b7cbb57 After G: a full delivery cycle by hand, as the operator asked on 2026-11-17 2026-11-17 09:22:37 +01:00
jschoubben 64ff3fd4e9 Answer A-465: the assigner's composition inputs end with their objects, and a drop tool for those left 2026-11-17 09:00:02 +01:00
jschoubben 782f90c003 Answer A-464e: the gate's start comparison ends only when every head was compared 2026-11-17 08:56:43 +01:00
jschoubben 5385c798c0 Answer A-463a and A-464d: a pending merge is not behind, and every source move is forward 2026-11-17 02:08:39 +01:00
jschoubben 163fe51f96 Answer A-464c: the gate's source moves a head only forward, and only when it changes 2026-11-17 02:00:59 +01:00
jschoubben acd7f1f588 Answer A-464b: what makes a merge one the gate did not make, and where that is said 2026-11-17 01:57:14 +01:00