Fix worker CLI tests for optional pool argument#64409
Closed
gopidesupavan wants to merge 1 commit intoapache:mainfrom
Closed
Fix worker CLI tests for optional pool argument#64409gopidesupavan wants to merge 1 commit intoapache:mainfrom
gopidesupavan wants to merge 1 commit intoapache:mainfrom
Conversation
Member
Author
|
closing in favour of https://github.com/apache/airflow/pull/64388/changes |
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.
Adjusted the celery worker CLI unit tests to match the current contract for --pool.
The required-arguments test no longer expects --pool prefork, since that flag is only added when celery.pool is present in config. Added a dedicated test that mocks the config-backed pool path and verifies both the forwarded --pool prefork argument and the corresponding maybe_patch_concurrency() call.
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.