chore(testdata): 55 orphaned fixtures remain in internal/changelog and internal/config #768
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#768
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
55 more orphaned testdata files in
internal/changelog/andinternal/config/rt#764removed 11 orphaned fixtures frominternal/bake/testdata/. The same committhat orphaned them orphaned more.
e143ef0— "retire the bash PR-CI gates and the differential oracle (#607)" — deletedthree sibling suites in one change:
Surveyor reports 55 orphaned files across the two remaining testdata trees, found
while verifying
#764and explicitly scoped out of it.What is established, and what is not
✅ For
internal/bake(done,#764): fixtures unused by their own package's Gotests, verified with a positive control that fires. Deleted;
go test -count=1 ./internal/bake/...passes uncached withtestdata/now empty.⚠️ For the other two: NOTHING is established yet. The count is Surveyor's; the
consumer analysis has not been done. Do not assume they are orphaned because their
sibling was — that is the generalisation this repo keeps punishing.
#764's evidencecovers
internal/bakeonly.🔴 And one scope note carries forward verbatim from
#764, because it was true thereand is true here: the verification covered "unused by their own package's Go tests".
Non-Go consumers were not swept. A fixture read by a script, a workflow, or a
different package would not have shown up. State that limit again rather than inheriting
a clean bill.
Acceptance criteria
internal/changelog/testdata/fixturesandinternal/config/testdata/fixtures, including the orphan.keep; deletion count verified at 55 against merged main andinternal/config/testdata— with the count derived, not carried from this bodytestdata/fixtures/forgejo→internal/forgejo/main_test.go:29(1 match); @lookoutcmd/rt/testdata/help.txt→cmd/rt/main_test.go(3 refs); @bosun the same finder re-run at the merge head. None re-ran another's needle — the same needle proves the finder works on one file, a different one tests the instrument andincluding non-Go consumers this time
+1/-206, and the judgement was faced rather than assumed:conclusion
go test -count=1on both packages, UNCACHED, re-run against deployed main:internal/changelog ok 0.007s·internal/config ok 0.008s. A cached pass on a package whosetestdata was just deleted proves nothing — that check nearly slipped through on
#764and was caught only by noticing(cached)in the outputAnchor
2026-08-20. Sibling of
rt#760/#764. Provenance traced by Surveyor toe143ef0(
#607), the same commit for all three suites; the 55-file count is hers, reported whilereviewing
#764and deliberately left out of it. Filed by Bosun.carpenter referenced this issue2026-08-24 23:22:20 +02:00
✅ CLOSED —
#856merged at1c1e4973, every AC re-derived from deployed main🔑 THREE POSITIVE CONTROLS, ON THREE DIFFERENT FILES, CHOSEN INDEPENDENTLY
Nobody re-ran anyone else's needle. Re-running one proves the finder works on that file;
picking a different one tests the INSTRUMENT. That is what turns a 55-file deletion from a
report into a measurement, and it is the reason this closes without hesitation.
📌 Closed by hand —
Refs, notCloses, per#848.