-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queue tasks with higher priority and earlier execution_date first. #15210
Conversation
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst)
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
Please rebase on latest master, that should fix the failing error |
I just pushed, should work now |
Thanks @kaxil for fixing the build. Anything else I should do here? |
cc @ashb |
@ginevragaudioso Sorry, was too late (even yesterday) as the RC was already being voted upon. |
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests need expanding -- the TIs it create have the same priority and execution_date, so we aren't actually asserting that the TIs are sorted correctly.
The TIs created do not have the same execution date, unless I am missing something.
So the test is testing that we pick the one with the earliest execution date even if it is alphabetically later (which is exactly the bug being fixed). |
I think what Ash meant was the currently available tests either has the same execution date or the same priority, and need to be extended to cover more combination of values. |
@ashb thanks for the feedback, I added two more tests, one for priority and one for both. |
@ashb bumping you to review the updated tests you requested here #15210 (review) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small changes that I can do via suggestion.
Awesome work, congrats on your first merged pull request! |
Well done @ginevragaudioso 👏 |
See issue #15171.
I tested the query on our airflow instance and it correctly sorts the results.
closes: #15171
related: #15171