jschoubben
5c20b9ef15
mesh-delivery-checker: the line test holds ADR 0591's case of a first failure longer than the forge's limit
...
The first failure's words are shortened; "failed (N)" and "and N-1 more" stay whole within the limit.
Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
2026-11-02 18:56:19 +01: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
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