AnachronautandClaude Opus 5
8fbbeb6ec9
The Test Manual said an xfail test records the assembler's refusal message and so catches both an error that stops being detected and a message that changes without anybody meaning it to. It did not. run.sh checked only that the assembler exited non zero, printed the first line for a person to read, and compared nothing; --bless recorded nothing for these sixteen tests at all. So an xfail passed four different ways that look identical from outside: the intended error fired, an unrelated error fired, the message changed, or the assembler fell over on its way to the point. That is the documentation describing behaviour the code does not have, which is the exact failure Tests/docs.sh exists to prevent, in the manual that argues for knowing what your evidence is worth. The diagnostic is now stripped of colour, given the same [exit N] line every other recorded result carries, and compared through check() like anything else. Sixteen results recorded; every existing one is byte for byte unchanged. Verified the way the manual asks: one diagnostic was broken on purpose, its test failed with the changed line in the diff, and its neighbour passed. Found by ChatGPT reviewing the manual. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
7 lines
313 B
Plaintext
7 lines
313 B
Plaintext
Error: The Program Segment is based at 0x2000, but the Data Segment
|
|
has 1 byte at 0x0000 and was never given a #Base.
|
|
Half a program loaded at zero lands on whatever is already there.
|
|
File: testPrograms/diagnostics/unbasedSegment.asm
|
|
Say "#Base 0x0000" in the Data Segment if that is what you meant.
|
|
[exit 1]
|