Add CeleryExecutor callback workload routing test#66435
Open
leeyspaul wants to merge 1 commit intoapache:mainfrom
Open
Add CeleryExecutor callback workload routing test#66435leeyspaul wants to merge 1 commit intoapache:mainfrom
leeyspaul wants to merge 1 commit intoapache:mainfrom
Conversation
Contributor
SameerMesiah97
left a comment
There was a problem hiding this comment.
Approved pending green CI.
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 focused CeleryExecutor unit coverage for routing
ExecuteCallbackworkloads through_process_workloads().This verifies that callback workloads are sent to Celery with:
This is intended to strengthen executor compatibility coverage for the Airflow 3.2+ callback workload path.
Related: #65793
Was generative AI tooling used to co-author this PR?
{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.