Commit Graph
3351 Commits
Author SHA1 Message Date
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
mesh-tools 36b66c0b54 Merge pull request 'Design 47 G: the lead's answers A-469w..A-470 (caps, settings, waits, bound keys)' (#672) from design/47-G-lead-answers-83 into main 2026-11-17 10:22:16 +00: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
mesh-tools ff464265b9 Merge pull request 'Design 47 G-23: the faults met on 2026-11-17' (#671) from design/47-G-after-delivery-notes-1117 into main 2026-11-17 10:17:35 +00: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
mesh-tools c94cbff169 Merge pull request 'Design 47 G: the lead's answer A-469v (a drop's answer; named run definitions)' (#670) from design/47-G-lead-answers-82 into main 2026-11-17 10:11:37 +00: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
mesh-tools 5880f85e5b Merge pull request 'Design 47 G: the lead's answers A-469t, A-469u (one shared form; the four run verbs)' (#669) from design/47-G-lead-answers-81 into main 2026-11-17 10:10:14 +00: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
mesh-tools 9c23309b38 Merge pull request 'Design 47 G: the lead's answers A-468..A-469s (G-24's prepare: 14 design questions, 20 design-meets-code)' (#668) from design/47-G-lead-answers-80 into main 2026-11-17 10:04:16 +00: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
mesh-tools be550d1790 Merge pull request 'Design 47 G: the lead's answer A-467a (a composition step with no machine judged never passes)' (#667) from design/47-G-lead-answers-79 into main 2026-11-17 09:48:03 +00:00
jschoubben 92f967f542 Answer A-467a: a composition step with no machine judged never passes 2026-11-17 10:47:50 +01:00
mesh-tools c2aae05b59 Merge pull request 'Design 47 G: one composition run per candidate and machine, one test run per module's packages (G-24)' (#666) from design/47-G-shared-runs into main 2026-11-17 09:41:41 +00: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
mesh-tools e82887d67c Merge pull request 'Design 47 G: the lead's answer A-467 (no composition passes on a machine it did not judge)' (#665) from design/47-G-lead-answers-78 into main 2026-11-17 09:35:27 +00: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
mesh-tools 2407183c70 Merge pull request 'Design 47 G: the lead's answer A-465b (the inputs key form is the assigner's own)' (#664) from design/47-G-lead-answers-77 into main 2026-11-17 08:46:28 +00: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
mesh-tools a550fb9256 Merge pull request 'Design 47 G: the lead's answer A-461c (the golden node grant checked against invokes); after G item 14' (#663) from design/47-G-lead-answers-76 into main 2026-11-17 08:40:06 +00: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
mesh-tools 1ac43e4ddf Merge pull request 'Design 47 G: the lead's answer A-465a (a composition input kept once per content)' (#662) from design/47-G-lead-answers-75 into main 2026-11-17 08:38:18 +00: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
mesh-tools 8fd85c6768 Merge pull request 'Design 47 G: after G, a full delivery cycle by hand (the operator, 2026-11-17)' (#661) from design/47-G-after-hand-cycle into main 2026-11-17 08:23:07 +00: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
mesh-tools 36d5b50d5b Merge pull request 'Design 47 G: the lead's answer A-465 (the assigner's inputs end with their objects)' (#660) from design/47-G-lead-answers-74 into main 2026-11-17 08:00:16 +00: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
mesh-tools 2b59494c30 Merge pull request 'Design 47 G: the lead's answer A-464e (the gate's start comparison ends only when every head was compared)' (#659) from design/47-G-lead-answers-73 into main 2026-11-17 07:56:55 +00: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
mesh-tools f0a940463b Merge pull request 'Design 47 G: the lead's answers A-463a and A-464d (from the review)' (#658) from design/47-G-lead-answers-72 into main 2026-11-17 01:08:47 +00: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
mesh-tools cf08f6e69b Merge pull request 'Design 47 G: the lead's answer A-464c (the gate's source moves a head only forward)' (#657) from design/47-G-lead-answers-71 into main 2026-11-17 01:01:11 +00: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
mesh-tools c81a186a3d Merge pull request 'Design 47 G: the lead's answer A-464b (a merge the gate did not make)' (#656) from design/47-G-lead-answers-70 into main 2026-11-17 00:57:23 +00: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
mesh-tools 6664193aac Merge pull request 'Design 47 G: the lead's answer A-464a (a read tool for the indexer's takeins state)' (#655) from design/47-G-lead-answers-69 into main 2026-11-17 00:50:39 +00:00
jschoubben d47f617ad5 Answer A-464a: a read tool for the indexer's takeins state, so a hand take-in is seen 2026-11-17 01:50:25 +01:00
mesh-tools 84ef09d4b4 Merge pull request 'Design 47 G: the lead's answer A-464 (the gate's source follows every merge)' (#654) from design/47-G-lead-answers-68 into main 2026-11-17 00:43:10 +00:00
jschoubben 709ad9de59 A-464: name mesh-host in a code span, as the words test asks 2026-11-17 01:42:59 +01:00
jschoubben a4d7d44cd0 Answer A-464: the gate's source follows every merge into a watched branch 2026-11-17 01:42:43 +01:00