Track T by default: the FAILING STEP named no owner. Line 1 of 25 is
livesrc=$(tools/compiler_srchash.sh); \ stampsrc=$(sed -n 's/^srchash //p' compiler/.pascal26.fixedpoint); \ if [ -z "$l. The job's ownsrc(tools/compiler_srchash.sh, 5 file(s)) is NOT used here on purpose: it is what the job compiles, not what broke, and guessing a lane from it is what sent three reds in one job to the wrong lane. This is a FALLBACK, not a finding — nothing says the defect is Track T's. Re-lane it before working it.
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-record-abi-mixed-link#src:tools/compiler_srchash.sh at 4c7c88d3614b in step 1/25, livesrc=$(tools/compiler_srchash.sh); \ stampsrc=$(sed -n 's/^srchash //p' compiler/.pascal26.fixedpoint); \ if [ -z "$… (auto-filed by twatch)
- Type: regression (auto-filed by Track T watcher, host seven, twatch
883da23adb0a). Untriaged. - Found: 2026-09-11T01:44:42Z
- Test source: tools/compiler_srchash.sh compiler/.pascal26.fixedpoint +3
- Failing step: line 1 of 25 of the job's recipe; it names
tools/compiler_srchash.sh compiler/.pascal26.fixedpoint.livesrc=$(tools/compiler_srchash.sh); \ stampsrc=$(sed -n 's/^srchash //p' compiler/.pascal26.fixedpoint); \ if [ -z "$livesrc" ]; then \ echo "tools/compiler_srchash.sh produced NO source hash, so this check cannot run."; \ echo " An empty result means 'could not measure', never 'measured and they
Repro
tools/testmgr.py --tier full --job 'test-record-abi-mixed-link#src:tools/compiler_srchash.sh' at 4c7c88d3614b97829c308df7ecbaf4361085f764
Range
The named sha
4c7c88d3614bCANNOT 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 4c7c88d3614b, last good 840b21cfcf5d, 1 commit(s) in range — the watcher narrows this by idle bisect; check tstate/TSTATE.md for the current range.
Log tail
compiler/.pascal26.fixedpoint was written for DIFFERENT SOURCES than the tree has.
stamp sources: <none — written before the stamp carried a source hash>
tree sources: cf8d110d8293743d39be7e301737e1e134d6c59a181b28399af2c9bf90cf6478
Stamp predates the srccount field, so set-vs-contents cannot be told apart.
It will be after the next rebuild.
Nothing untracked or modified locally, so no stray file explains it:
this stamp was written for a DIFFERENT TREE. Usual cause is a pull
-- or a sync, which pulls -- with no rebuild after it.
A stamp NEWER than sources it does not describe is how this step
printed 'verified' three times in one day without building anything.
Recover with: rm -f compiler/.pascal26.fixedpoint && make compiler/pascal26
Stub ticket: signal only. Track T agent (face 2) enriches or a dev track takes it from the repro line.
Log
- 2026-09-11 — the seven watcher saw
test-record-abi-mixed-link#src:tools/compiler_srchash.shGREEN at 24a4733f5bff (tier full) and did NOT close this: this is a repeat stub (regression-test-record-abi-mixed-link-compiler-srchash-2, notregression-test-record-abi-mixed-link-compiler-srchash) — the job already went red, was closed, and came back, so one green is the outcome a live intermittent bug produces most of the time. The green is recorded because it is evidence and because a ticket that stops moving with no reason reads as forgotten; closing this one is a human's call.