Skip assertNoZombies check on non-Docker-based tests
#302
Conversation
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
strangelookingnerd
approved these changes
Nov 6, 2025
jtnord
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Like #301, amending #291 & #274. As far as I can tell the issue in jenkinsci/bom#5931 (comment) is that the zombie process check works on the VM-based agents used in this plugin’s own CI but fails in the K8s agents used by
bomCI. Unclear why this would be failing now. At any rate, the non-Docker-based tests run in an undefined Linux host environment which we cannot control, whereas the zombie check was intended to correct a regression in a containerized agent.