Kill Postgres harder in fuzzer workflow - #10000
Merged
Merged
Conversation
It can get stuck after address sanitizer failure due to an upstream bug with race condition in terminating the background workers. This leads to repro failure.
|
@kpan2034, @svenklemm: please review this pull request.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
natalya-aksman
approved these changes
Jun 8, 2026
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
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.
It can get stuck after address sanitizer failure due to an upstream bug with race condition in terminating the background workers. This leads to repro failure.
The upstream bug: https://www.postgresql.org/message-id/flat/CALzhyqxD2_0HGn4zz5agovrGF5hsGebUw8SUK%2BJdTpXxd9nsyQ%40mail.gmail.com