-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Make test_scheduler_job work locally after moving examples #50917
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
Make test_scheduler_job work locally after moving examples #50917
Conversation
rawwar
left a comment
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.
Thanks!
ed8c97b to
5fd46ff
Compare
|
OK. seems that parts of the |
There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
5fd46ff to
b838702
Compare
sunank200
left a comment
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.
Awesome!
) There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
) There was an issue with the test after migrating standard provider examples to ... standard provider (apache#49978) that made the test work only in Breeze and not in local env.
There was an issue with the test after migrating standard provider examples to ... standard provider (#49978) that made the test work only in Breeze and not in local env.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.