test(b5): treat zombie pane processes as stopped - #117
Open
Florious95 wants to merge 1 commit into
Open
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
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.
Goal: close the v0.5.69 Ubuntu B5 residual-sweep red without weakening leader/server survival.
Root cause: the integration fixture used kill -0 as a running-process predicate. On Unix kill -0 also succeeds for an exited but not-yet-reaped zombie. The historical Ubuntu failure spent the long residual-loop path and then reported only the worker PID as alive; neither the leader nor tmux server was reported dead. The fixture therefore misclassified a terminated worker as running.
Change: read ps STAT, treat Z as stopped, and include STAT in future worker failure output. The leader and tmux server use the same strict predicate, so a zombie leader/server still fails the survival contract.
Validation at head f34b1d7:
No product lifecycle behavior, timeout, retry, serialization, or assertion scope changed.