← board

Track guessed as P from the FAILING STEP — line 1 of 2, ./compiler/pascal26 -Fulib/rtl test/test_pchar_from_a_string_literal.pas /tmp/test_pcharlit26, which names test/test_pchar_from_a_string_literal.pas. Not from the job's name or its src: those describe what the job is ABOUT, and this job's recipe spans 2 source file(s). 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 8 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_pchar_from_a_string_literal.pas at f2c6ff3288b4 in step 1/2, ./compiler/pascal26 -Fulib/rtl test/test_pchar_from_a_string_literal.pas /tmp/test_pcharlit26 (auto-filed by twatch)

Repro

tools/testmgr.py --tier native --job 'test-core#src:test/test_pchar_from_a_string_literal.pas' at f2c6ff3288b407ca08ee7e469f4b2a8b56f98972

Range

The named sha f2c6ff3288b4 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 f2c6ff3288b4, last good 7867c5481c01, 2 commit(s) in range — the watcher narrows this by idle bisect; check tstate/TSTATE.md for the current range.

Log tail

pascal26:85: error: incompatible types: cannot assign Char to Pointer
(tail)
pascal26:85: error: incompatible types: cannot assign Char to Pointer

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

Log