test: report missing kubectl checks as skipped - #1243
Merged
jayminwest merged 1 commit intoSep 4, 2026
Conversation
Owner
|
Great work @joerosbury, thanks for the PR! |
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.
Summary
kubectlavailability once when the manifest test module loadstest.skipIf(...)kubectlis availablePreviously, when
kubectlwas unavailable, the two tests printed a warningand returned normally. Bun and JUnit therefore reported those checks as
passing instead of skipped.
Validation
Without
kubectl:skipped="2"With checksum-verified
kubectlv1.37.0 available:Repository validation:
git diff --check: passedThe two optional Linux+bwrap sandbox tests were skipped in the controlled
validation environment because
bwrapwas intentionally unavailable; nobwrap-related source changes are included in this PR.
Fixes #1233