← board

regression: test-c-conformance-arm32#shard2/6 red at 96b6bac331d9 (auto-filed by twatch)

Repro

tools/testmgr.py --tier full --job 'test-c-conformance-arm32#shard2/6' at 96b6bac331d9d8b9c838d0055a8e3841157314f1

Range

bad 96b6bac331d9, last good 96b6bac331d9, 0 commit(s) in range — the watcher narrows this by idle bisect; check tstate/TSTATE.md for the current range.

Log tail

FAIL 00219.c — output mismatch:
    --- library_candidates/c-testsuite/tests/single-exec/00219.c.expected	2026-07-07 21:11:07.000000000 +0200
    +++ /tmp/pxx_c_conformance.213858/out.txt	2026-07-12 19:36:54.306517306 +0200
    @@ -6,7 +6,7 @@
     0
     5
     1
    -2
    +1
test-c-conformance-arm32: 36 pass, 1 fail, 0 skip (of 37)
test-c-conformance-arm32: FAILURES: 00219.c(output)

Stub ticket: signal only. Track T agent (face 2) enriches or a dev track takes it from the repro line.

Triage: not a regression. bad == last good == 96b6bac331d9, 0 commits in range — this job was newly enrolled at eb63555d (cross-conformance matrix), so this is a first measurement of a pre-existing cross-target gap, not a break caused by a commit in range. The underlying bugs are tracked in their owning lanes: [[bug-c-generic-long-vs-int-on-32bit]] (00219), [[bug-c-lshift-promotion-aarch64]] (00200), [[bug-c-struct-byval-varargs-32bit]] (00204). The tests are still red; this stub is retired only because it duplicates those three.