mesh-delivery-checker: a failure's words are never "PASS"; with no cause, take the runtime's line or say so (issue 1901) #43

Merged

jschoubben merged 3 commits from fix/1901-package-cause into main 2026-10-25 15:07:47 +00:00

Conversation 1 Commits 3 Files Changed 2

+178 -11

3 Commits

Author	SHA1	Message	Date
jschoubben	dd9138310c	mesh-delivery-checker: a package sent as its FAIL line alone is still worded, and the words keep their bound exactly (issue 1901, review round 1) ... The build module on main sends a timeout, exit or kill as only 'FAIL <pkg>': dropping summary lines left empty words. They now say the package failed with no cause sent. Causes match at column 0 only, summary lines only in go's exact forms, and the words count the cause, the marker and the newlines within MaxWords.	2026-10-25 15:58:09 +01:00
jschoubben	f72f57f6e2	mesh-delivery-checker: with no cause told apart, a race report is the cause (issue 1901) ... An older build module's output for a race after the tests' PASS is now worded by the race's heading, access and frame, not by go test's PASS or the report's separator line (1901/AC5).	2026-10-25 15:52:21 +01:00
jschoubben	6d2d50b1e1	mesh-delivery-checker: a failure's words are never "PASS"; with no cause, take the panic line (issue 1901) ... A try of mesh-controller's status read 'cmd/mesh-controller: PASS': the build module sent a package failure whose output began with go test's PASS. The checker now drops go test's summary lines, takes the first panic, fatal error or signal line as the cause when the build module told none apart (read before the words are cut), says the tests passed and the program failed after them when nothing else is left, and cuts a cause to 1 KB so the words keep their bound (1901/AC5).	2026-10-25 15:38:40 +01:00