tools: resolve the module root from the harness, not from its own directory

The harness derived the module root from its own location, so moving it into
tools/ pointed every path at tools/pkg/... and it failed on the first mutation.
A mutation harness that cannot run is worse than none: its output is the evidence
that a test can fail for the right reason, and an unrunnable one leaves that
claim resting on when it last ran. 30/30 killed from the new location.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-07-29 11:17:45 -07:00
co-authored by Hanzo Dev
parent 5736ea8168
commit 7392747d24
+2 -1
View File
@@ -6,7 +6,8 @@ Reports per mutation: ANCHOR MISS (not applied -> not a kill), COMPILE FAIL
"""
import subprocess, sys, os, shutil
ROOT = os.path.dirname(os.path.abspath(__file__))
# The module root, one level above this script, so the harness runs from anywhere.
ROOT = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
ENV = dict(os.environ, TMPDIR="/tmp", GOWORK="off",
PATH="/usr/local/go/bin:" + os.environ["PATH"])