test: drain API workers before removing fixture state - #45
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
1 participant
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.
The unauthenticated-read API test could remove its temporary state while a daemon request worker was still writing its post-response access log. This caused the Python 3.11 coverage run to fail with a nonempty-directory cleanup error after its HTTP assertions had passed.
Use the Zeus server and existing bounded fixture drain helper, and explicitly close the HTTP connection. Preserve both authorization assertions and cleanup failures; application behavior is unchanged.
Validation: four targeted API fixture tests passed with ResourceWarning treated as an error.
make checkpassed: 1,558 tests twice (three platform skips per run), 83.91% source/branch coverage, repository checks, Ruff, mypy, Bandit, and ShellCheck.