mesh-delivery

testdata/captured

Keep nothing for a workspace given siblings, place the siblings where the tests state them, decide the hold from the listed plan keys (review D1-D3)

2026-10-21 21:52:41 +02:00

awaiting_test.go

Wait for the assigner's composition only while the assigner is online, say at once that it is not judged when it is not, and take it in when the assigner writes it later, so no check waits its bound for a composition nobody makes (issue 1297, B3d)

2026-10-23 15:44:00 +02:00

awaiting.go

Wait for the assigner's composition only while the assigner is online, say at once that it is not judged when it is not, and take it in when the assigner writes it later, so no check waits its bound for a composition nobody makes (issue 1297, B3d)

2026-10-23 15:44:00 +02:00

beside.go

Place mesh-controller beside the node-engine's tests, which read its manifest (issue 1295, R4g)

2026-10-23 18:36:13 +02:00

builds.go

The checker's line says whether each candidate module's build is built, failed or waiting, read from the builder's keys (issue 1684)

2026-10-21 21:29:13 +02:00

case.go

Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)

2026-10-23 16:11:43 +02:00

checker_test.go

Stop watching the node-engine's have in the checker: a check's asks wait in the build seats' streams, which redeliver a lost node's ask, so no check fails for want of a node; presence stays for an unheard forge and the assigner's presence (issue 1912)

2026-10-23 16:41:34 +02:00

checker.go

Merge remote-tracking branch 'origin/feat/r4g' into feat/r4g

2026-10-23 16:46:05 +02:00

composition_test.go

Read the assigner's composition into the checker's verdict in place of 'not yet run', failing a check whose composition failed, naming its machine (issue 1297, subtask B3d; ADR 0528 clause 5)

2026-10-23 15:27:59 +02:00

digestform_test.go

Read a level's digest from mesh-sdk's list form, so kept verdicts hold for a check whose end names a package like token (issue 1930)

2026-10-23 23:37:49 +02:00

doc.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

examiner_test.go

Prove that a second check of the same heads keeps every package the first passed, the digest being taken inside the check ask as the build module answers it (issue 1917)

2026-10-23 17:18:37 +02:00

failure_words_test.go

Test 1901/AC3: an older pair of build module and checker still agree (issue 1901)

2026-10-23 22:14:29 +02:00

fakes_test.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

gate_test.go

Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)

2026-10-23 16:11:43 +02:00

heard_test.go

Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)

2026-10-23 16:05:55 +02:00

heard.go

Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)

2026-10-23 16:05:55 +02:00

judge.go

Merge pull request 'The checker keeps a failed test's whole message with its cause first, and its status names the cause (issue 1901, with mesh-catalog)' (#30 ) from fix/1901-rebased into main

2026-10-23 22:36:03 +00:00

judged_test.go

Place the change's own repository beside it at its trunk, so a shrink-only list test compares with the trunk's copy at $MESH_CHECK_BESIDE/<name> (issue 1887 A12, ADR 0529 §2)

2026-10-23 15:35:37 +02:00

kept_test.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

kept.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

line_test.go

Say the unit level's gofmt and go vet time in the check's line, and pin the group's mesh-sdk head that carries it (issue 1887 D7-go, review round 2 item 5)

2026-10-23 16:51:55 +02:00

line.go

mesh-delivery-checker: a failed test's verdict keeps its last lines and the status line names its error (issue 1901)

2026-10-23 22:13:41 +02:00

pins_test.go

Place mesh-controller beside the node-engine's tests, which read its manifest (issue 1295, R4g)

2026-10-23 18:36:13 +02:00

pins.go

Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)

2026-10-23 16:05:55 +02:00

preview_named_test.go

Carry each named path's object from a fetch's module trees into the merge preview, so the indexer narrows a candidate's tree as the merge's (issue 1758, I8, ADR 0499 §2)

2026-10-22 18:15:09 +02:00

preview.go

Carry each named path's object from a fetch's module trees into the merge preview, so the indexer narrows a candidate's tree as the merge's (issue 1758, I8, ADR 0499 §2)

2026-10-22 18:15:09 +02:00

rank_test.go

Stop watching the node-engine's have in the checker: a check's asks wait in the build seats' streams, which redeliver a lost node's ask, so no check fails for want of a node; presence stays for an unheard forge and the assigner's presence (issue 1912)

2026-10-23 16:41:34 +02:00

read_test.go

Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)

2026-10-23 16:11:43 +02:00

read.go

Say in the checker's status that a check without a verdict waits in a build seat's stream, not behind a plan key or a capacity, as A5b left it (issue 1887, review round 2 item 4)

2026-10-23 16:47:20 +02:00

results.go

mesh-delivery-checker: a failed test's verdict keeps its last lines and the status line names its error (issue 1901)

2026-10-23 22:13:41 +02:00

store.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

try_test.go

Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)

2026-10-23 16:11:43 +02:00

try.go

Bound a build or check ask's step from its start, and drop the checker's whole-check bound, so asks waiting in the streams during a large rebuild are never failed and asked twice (issue 1887, review round 2 item 1; ADR 0525 §3, §6)

2026-10-23 16:45:35 +02:00