Repository navigation
Check that test_close_writer stops the worker threads - #303
Merged
rhpvorderman merged 1 commit intoOct 28, 2026
Merged
Conversation
Use assert_writer_closed(), which the error tests already use. It also checks that the threads are no longer alive.
Collaborator
|
Thanks again! |
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.
test_close_writerchecks onlyf.closed. This PR usesassert_writer_closed(), which the error tests already use. It also checks that the compression and output threads have stopped.To test it, I changed
close()to callstop()only after an error. The test passes ondevelopand fails with this PR.This PR changes only tests, so it has no CHANGELOG entry.
Checklist