Repository navigation
Fix leaked triggerer thread in test_trigger_logger_fd_closed_when_removed - #70941
Merged
Merged
Conversation
amoghrajesh
requested review from
bugraoz93,
eladkal,
henry3260,
jason810496,
potiuk and
shahar1
August 2, 2026 12:54
eladkal
approved these changes
Aug 2, 2026
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Aug 14, 2026
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
1 task done
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.
Was generative AI tooling used to co-author this PR?
Noticed in https://github.com/apache/airflow/actions/runs/30739444883
Error:
The test started a real TriggerRunnerSupervisor subprocess but only killed it after the final assertion, so a failed or slow assertion left the subprocess running. The leaked process kept calling
time.monotonic()in the background, polluting mock call counts in unrelated tests that patch the same target later in the same run.{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.