Repository navigation
Retry Docker readiness probes that time out with SIGPIPE - #8
Merged
Merged
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.
Docker readiness probes can hit their 15-second local deadline and exit with SIGPIPE while shutting down. The action treated these as permanent command failures because it recognized only SIGTERM, causing healthy Gen2 builders to fail setup. Recognize deadline-killed children independently of the final signal, retaining the existing bounded read-only retry policy.
Validation: builder action tests passed, including real subprocess regressions for deadline-triggered SIGPIPE and an ordinary SIGPIPE failure that must remain non-retryable. No build or push is replayed.