Repository navigation
Support connection-test workloads in CeleryExecutor - #74928
Open
anishgirianish wants to merge 1 commit into
Open
anishgirianish wants to merge 1 commit into
anishgirianish wants to merge 1 commit into
Conversation
anishgirianish
requested review from
dheerajturaga and
hussein-awala
as code owners
October 17, 2026 17:58
anishgirianish
force-pushed
the
celery-connection-test-workload
branch
from
October 17, 2026 18:01
d706579 to
f0fe5c0
Compare
This branch has not been deployed
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.
Adds
TEST_CONNECTIONworkload support toCeleryExecutorso async connection tests (#62343) can run on Celery workers.Prerequisite for #68113.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5.1) following the guidelines
{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.