Repository navigation
test: expose fixture progress on ownership smoke failures - #669
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
enabled auto-merge (squash)
September 15, 2026 21:32
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
blove
temporarily deployed
to
vercel-preview
September 15, 2026 21:32 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The renamed-resource smoke test can report a missing replacement when a fake command times out before the fixture ever creates it. Include mutation progress, listing count, stderr and recent commands in that assertion's failure message so the next occurrence distinguishes an unreached mutation from a deleted replacement.
This changes only diagnostics. Assertions, timeouts, runtime behavior and CI configuration are unchanged. Related to #535; this does not establish that its historical ownership or runtime timeout signatures are fixed.
Validation: all 807 Kubernetes compatibility tests passed on the investigation baseline with Helm required; all six renamed-ownership cases passed after this diagnostic change. Scoped Biome and whitespace checks passed. A disposable 2,100 ms listing-delay probe reproduced the early-timeout path and was removed. Independent review found no actionable issues.