← board

origin/master has advanced 2 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_val_builtin.pas red at 7462448a21bd (auto-filed by twatch)

Repro

tools/testmgr.py --tier native --job 'test-core#src:test/test_val_builtin.pas' at 7462448a21bd6d106d58b6b07faf6d240f188a1b

Range

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

Log tail

ok: /tmp/testmgr-scratch-657947/test_val_builtin26  [code=94437B  data=2760B  bss=9644B  procs=202]

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

Resolved 2026-08-16 — the EXPECTATION was wrong, not the code

bug-p-val-rejects-the-radix-prefixes taught Val FPC's prefixes, and x is one of them: a bare hex prefix with no digits stops one PAST itself, so FPC 3.2.2 answers 0 2 where this test asserted 0 1. The old expectation encoded pxx's behaviour from when no prefix was recognised at all.

Measured on FPC before changing it (the whole point of the fix), so the test and its Makefile line now assert FPC's answer, with the reason written into the test beside the line. The prefixes themselves are covered by test/test_val_radix_and_optional_code.pas.