← board

Track guessed as P from the test source. The failing step (line 2 of 2) named no source of its own, but this job has only ONE source — so first-source and only-source are the same file here and there is no other lane in frame. The ranker reads frontmatter, so this line — not the body — decides who works it; correct it if the guess is wrong.

origin/master has advanced 10 commit(s) since this sha. Re-verify at current HEAD before acting — the callback is tagged to the sha that was tested, which may no longer be the state of the tree.

regression: test-core#src:test/test_multithreading.pas@1 at 039be8b4aa97 in step 2/2, /tmp/test_multithreading26 | grep -q "multithreading test completed successfully" (auto-filed by twatch)

Repro

tools/testmgr.py --tier native --job 'test-core#src:test/test_multithreading.pas@1' at 039be8b4aa97ff662460ce2a0d65b314e0b7c134

Range

The named sha 039be8b4aa97 CANNOT be the cause — it touches no buildable file (docs / tickets / tstate only). It is the sha that was TESTED, i.e. the upper bound of an untested range; the cause is somewhere below it.

bad 039be8b4aa97, last good 12c916c5c9ca, 4 commit(s) in range — the watcher narrows this by idle bisect; check tstate/TSTATE.md for the current range.

Log tail

Segmentation fault (core dumped)
(tail)
ok: /tmp/testmgr-scratch-2539273/test_multithreading26  [code=69288B  data=3988B  bss=43556B  procs=138]
Segmentation fault (core dumped)

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

Log