tomsawyerhu/nano-harness/test-failure-triage

failure type:
smallest failing command:
observed output:
expected output or contract:
likely cause:
next command:
next edit:

missing executable/artifact
permission error
compile error
missing dependency
wrong stdout
wrong stderr
wrong exit code
exception type/message mismatch
wrong API signature/import path
file side-effect mismatch
timeout/performance
test harness/environment issue
empty or invalid eval result

cmd > /tmp/fail.out 2> /tmp/fail.err; code=$?
echo "exit=$code"
tail -80 /tmp/fail.out
tail -120 /tmp/fail.err

rg -n "error|failed|failure|panic|traceback|exception|expected|actual|assert|not found|permission|timeout" /tmp/fail.out /tmp/fail.err

stdout
stderr
exit_code

import path
function/class name
argument handling
return value
exception type
exception message
side effects

build command
generated artifact path
executable bit
runtime dynamic library errors
missing tool or dependency

missing executable -> inspect compile.sh and expected output path
permission error -> chmod executable or fix compile.sh
compile error -> fix first compiler error, not all later cascades
missing dependency -> avoid new dependency; use standard library or vendored code
wrong stdout/stderr -> create one golden case and diff
wrong exit code -> inspect argparse/error path or exception handling
API mismatch -> inspect tests/imports before changing behavior
timeout -> reduce algorithmic complexity or add fast path
empty eval -> inspect eval file/container/log, not implementation first