AnachronautandClaude Opus 5
b1dde7908c
A held thruster burns every tick it is held for, which is the whole reason the pad exists: the console can only say a key went down, so a thruster driven by it could be pumped and never leaned on. The burn happens on the same tick gravity does, and for the same reason - a sixteenth of a pixel is the smallest step this arithmetic takes, and applied sixty times a second it is an enormous acceleration. On the tick, thrust and gravity are two numbers whose RATIO is the whole feel of the thing. Position still moves every frame; only the acceleration is stepped, and nothing can see that. Two against gravity's one, so climbing and falling are the same speed. Three was the first try and it left the moon after about a second of holding. If there is a pad the console's arrows are ignored, because under a window the same keypress reaches both - the pad as a level, the console as a byte - and a thruster that fired twice for one press would be a mystery to anybody tuning it. q still quits, since a pad has no letter for it. With no pad the arrows still burn once a press, which is the most that can be done down a wire. And break.sh now rebuilds the disk images as well as the binaries. Half the things worth breaking here are SplitBit assembly rather than C, and those live on the fixture disks - so an edit to a .asm file changed nothing the suite could see, and the tool reported that nothing caught the break. That is the exact lie it was written to prevent, turning up in a new place. With the disks rebuilt it catches this one: the lander falls between the two captures instead of climbing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
125 lines
4.5 KiB
Bash
Executable File
125 lines
4.5 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Breaks something on purpose and checks that a suite notices.
|
|
#
|
|
# ---- Why this is a script and not a thing to type each time ----
|
|
#
|
|
# A check that passes proves nothing until it has been seen to fail. Typing that by hand went
|
|
# wrong twice in two days, and BOTH TIMES IT LOOKED LIKE A RESULT: the suite ran, went green,
|
|
# and read exactly like "this check does not catch that".
|
|
#
|
|
# Once the edit produced code that would not compile. make failed, the exit status was not
|
|
# looked at, and the PREVIOUS binary ran the suite.
|
|
# Once the anchor was right but the filename was wrong, so nothing was edited at all.
|
|
#
|
|
# Neither had anything to do with the build system - headers have always rebuilt what depends
|
|
# on them. What was missing was a harness that refuses to report a result it did not earn. So
|
|
# every step below is checked, and anything unexpected is a hard error rather than a green
|
|
# run: NOT FINDING THE BREAK IS THE ANSWER THIS TOOL EXISTS TO GIVE, and it is worthless if it
|
|
# can also be the answer when the break never happened.
|
|
#
|
|
# Usage:
|
|
# ./Tests/break.sh <file> <anchor> <replacement> <suite> [suite ...]
|
|
#
|
|
# The anchor must appear EXACTLY ONCE in the file. The file is restored afterwards whatever
|
|
# happens, including on an interrupt.
|
|
#
|
|
# Written by Anachronaut
|
|
|
|
set -u
|
|
|
|
ROOT="$(cd "$(dirname "$0")/.." && pwd)"
|
|
GREEN=$'\033[32m'; RED=$'\033[31m'; RESET=$'\033[0m'
|
|
[ -t 1 ] || { GREEN=""; RED=""; RESET=""; }
|
|
|
|
die() { printf '%sbreak.sh: %s%s\n' "$RED" "$1" "$RESET" >&2; exit 2; }
|
|
|
|
[ $# -ge 4 ] || die "usage: break.sh <file> <anchor> <replacement> <suite> [suite ...]"
|
|
|
|
FILE="$1"; ANCHOR="$2"; REPLACEMENT="$3"; shift 3
|
|
[ -f "$FILE" ] || die "no such file: $FILE"
|
|
|
|
# ---- The file comes back whatever happens ----
|
|
#
|
|
# Including a Ctrl-C in the middle of a suite, which is a thing that happens: a half broken
|
|
# working tree that looks fine is worse than any failing test.
|
|
KEEP="$(mktemp)"
|
|
cp "$FILE" "$KEEP"
|
|
restore() {
|
|
cp "$KEEP" "$FILE"; rm -f "$KEEP"
|
|
(cd "$ROOT" && make >/dev/null 2>&1 && ./Tests/makedisks.sh Tests/build >/dev/null 2>&1)
|
|
}
|
|
trap restore EXIT INT TERM
|
|
|
|
# ---- The edit, and proof it happened ----
|
|
python3 - "$FILE" "$ANCHOR" "$REPLACEMENT" <<'PY' || die "the edit did not apply"
|
|
import sys
|
|
path, anchor, replacement = sys.argv[1], sys.argv[2], sys.argv[3]
|
|
text = open(path).read()
|
|
seen = text.count(anchor)
|
|
if seen == 0:
|
|
sys.stderr.write("anchor not found in %s\n" % path)
|
|
raise SystemExit(1)
|
|
if seen > 1:
|
|
sys.stderr.write("anchor appears %d times in %s; it must be unique\n" % (seen, path))
|
|
raise SystemExit(1)
|
|
open(path, "w").write(text.replace(anchor, replacement))
|
|
PY
|
|
|
|
# ---- The build, and proof of that too ----
|
|
#
|
|
# And the disk images after it, because half the things worth breaking are SplitBit assembly
|
|
# rather than C, and those live on the fixture disks rather than in the binaries. Rebuilding
|
|
# only the emulator meant an edit to a .asm file changed nothing the suite could see and the
|
|
# tool reported that nothing caught the break - which is the exact lie it exists to prevent,
|
|
# turning up in a new place.
|
|
if ! (cd "$ROOT" && make) > "$KEEP.build" 2>&1; then
|
|
printf '%sbreak.sh: the broken version does not build, so nothing was tested%s\n' \
|
|
"$RED" "$RESET" >&2
|
|
tail -5 "$KEEP.build" >&2
|
|
rm -f "$KEEP.build"
|
|
exit 2
|
|
fi
|
|
rm -f "$KEEP.build"
|
|
|
|
if ! (cd "$ROOT" && ./Tests/makedisks.sh Tests/build) > "$KEEP.disks" 2>&1; then
|
|
printf '%sbreak.sh: the disks did not build, so nothing was tested%s\n' "$RED" "$RESET" >&2
|
|
tail -5 "$KEEP.disks" >&2
|
|
rm -f "$KEEP.disks"
|
|
exit 2
|
|
fi
|
|
rm -f "$KEEP.disks"
|
|
|
|
# ---- And then the suites ----
|
|
#
|
|
# A suite that fails is the GOOD outcome here, so the exit status is inverted: this reports
|
|
# success when the break was noticed.
|
|
NOTICED=0
|
|
for suite in "$@"; do
|
|
name="$(basename "$suite" .sh)"
|
|
if [ -x "$ROOT/Tests/$name.sh" ]; then
|
|
run="$ROOT/Tests/$name.sh"
|
|
elif [ -x "$suite" ]; then
|
|
run="$suite"
|
|
else
|
|
die "no such suite: $suite"
|
|
fi
|
|
printf -- '---- %s ----\n' "$name"
|
|
if "$run" 2>&1 | tee "$KEEP.out" | grep -E '^\s*\[FAIL\]' | sed 's/^ *//'; then
|
|
:
|
|
fi
|
|
if grep -qE '^[0-9]+ passed, [0-9]+ failed' "$KEEP.out"; then
|
|
NOTICED=1
|
|
grep -E '^[0-9]+ passed, [0-9]+ failed' "$KEEP.out" | tail -1
|
|
else
|
|
printf '%s%s did not notice%s\n' "$RED" "$name" "$RESET"
|
|
fi
|
|
rm -f "$KEEP.out"
|
|
done
|
|
|
|
if [ "$NOTICED" = "1" ]; then
|
|
printf '%sThe break was caught.%s\n' "$GREEN" "$RESET"
|
|
exit 0
|
|
fi
|
|
printf '%sNOTHING CAUGHT THE BREAK.%s\n' "$RED" "$RESET"
|
|
exit 1
|