Merge pull request 'Design 47 G-23: causes found on 2026-11-17' (#681) from design/47-G-after-delivery-notes-1117b into main
This commit was merged in pull request #681.
This commit is contained in:
@@ -187,7 +187,17 @@ deals with it, which is how the list is kept true.
|
||||
several times a minute, that "the manifest of the running build of" about 100 modules "cannot be read, so what the
|
||||
module graph says they serve is counted as served". Cause not yet known: nearly every module is named, so the
|
||||
assigner reads the running builds' manifests where none is kept. Being the second meeting, its fix is folded into
|
||||
G-24's assigner change once A1 to A7 are built.
|
||||
G-24's assigner change once A1 to A7 are built. Cause found the same day: the assigner reads a running build's
|
||||
manifest only from the builder's end in its stream, which the builder has said only since 2026-11-11, so no build
|
||||
made before then has one. G-24 says the list once per change of the set; after G, the builder says the end of each
|
||||
build it keeps into its stream once (principle 1; the alternative, reading the catalog entry at that fingerprint,
|
||||
reads another module's data).
|
||||
- **The Node build modules disagree on their toolchain.** On 2026-11-17 shanks's recipe differed from the other three
|
||||
nodes', and g14 ran Node v26.13.1 against v26.13.0, so no version and recipe held a majority, and lidarr, radarr and
|
||||
gitea had no fingerprint at revision 449 (A-470j keeps that from leaving whole machines not judged). After G: one
|
||||
version and one recipe declared through the mesh on every build node.
|
||||
- **The catalog had not taken in the node-engine's merge #234** by revision 450 (2026-11-17 about 11:50 CET), and the
|
||||
indexer's module reads answered "no responders": read why after G-24's delivery.
|
||||
- **The builder's and teller's integration tests fail only the 30 s setup bound under load**, and pass idle: the bound's
|
||||
kind (a setup bound judged on a busy build node) is decided after G.
|
||||
- The runner's journal floods with ends that name `pipeline ""`: the build seats' run asks are heard on the runner's
|
||||
|
||||
Reference in New Issue
Block a user