10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d2eb3e5ecf	checker: the line of a carried verdict names the head on the new trunk, then where it was carried from; a verdict being carried is pending and says so (ADR 0548 §6, §8; issue 568 D6)	2026-10-26 11:35:16 +01:00
jschoubben	04a56b7aff	Name every failed test in a check's verdict and a try's failed list (issue 1921) ... The checker stopped reading a level's test results at the first that did not pass and kept only its first failure, so a check named one fault per round. It now reads and counts every result and writes every failed test with its first line into the verdict's Failures and the try's failed list (at most 50, then how many more); Failed keeps the first one's words whole (issue 1901). Pins mesh-sdk fix/1921-every-failure.	2026-10-26 10:58:13 +01:00
jschoubben	0373a3b24e	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
jschoubben	d3561923aa	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
jschoubben	7cbb1c4207	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
jschoubben	2bdb8d0e00	Ask the Go build module to run the candidate when a merge changes it, and say in the line which program judged (issue 1898 K3) ... A change to mesh-build-go was judged by the installed module it replaces, so such pull requests were merged by hand. ADR 0535 §1, §2, §4, §5.	2026-10-23 14:06:57 +02:00
jschoubben	03eaf332ad	Say the composition's time and the machines it composed in a check's line, once the assigner reports them (issue 1300, C10) ... The line said only that the composition passed with an SDK commit, and its time sat among the parts that are dropped first, so a forge status never said how long the composition took or which machines it covered.	2026-10-22 18:06:07 +02:00
jschoubben	fecabfca8b	Fit the status line in the forge's 140 characters by giving the times and counts in their compact form before dropping them (issue 1682)	2026-10-21 21:30:24 +02:00
jschoubben	96ba6bd3dc	Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)	2026-10-21 21:20:42 +02:00
jschoubben	27072a01b5	Add the checker module: it watches the candidates, claims a verdict once, owes the status mesh/check and ends a check past its bound (issue 1678)	2026-10-21 21:07:14 +02:00