fix(drill): refuse to judge #16 on a broken baseline #31
No reviewers
Labels
No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:cli
scope:drill
scope:host
scope:installer
scope:templates
scope:tiers
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/box#31
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/drill-no-verdicts-on-broken-baseline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Run 7's box had no network before a single hardening change was applied — a clone/source IP collision had taken it down. Phase D measured anyway, and reported:
It does not. The box was already broken. Had I banked that, #16 would have been redesigned around a fiction — for the second time in this audit (the first was the B3
dns.mode=none"veto" I had to retract when runs 2 and 3 disagreed).The fix
Phase D is now gated on baseline egress passing. If the box can't reach the internet before hardening, the drill says so loudly and refuses to produce verdicts:
Also: the
dns.mode=nonerejection stops swallowing Incus's error message (2>/dev/null). The message is the finding — run 7 reported "incus rejected dns.mode=none" with no reason, and that reason is exactly what #16 needs.RUNS.mdgains trap 9: check that the thing you are measuring with still works before you trust what it tells you. Same failure as the B3 flip, different costume — and this drill has now produced two false design verdicts against #16, which is a worse failure mode than hanging.🤖 Generated with Claude Code