Add example for list-import-errors as a CI check#32811
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/main/CONTRIBUTING.rst)
|
|
This file is restructuredText, not Markdown, you need to fix the syntax. |
|
My apologies, just started writing on autopilot. I think it is fixed now. |
There was a problem hiding this comment.
| NOTE: For this to work accurately, you must ensure Airflow does not log any additional text to stdout. For example, you may need to fix any deprecation warnings, or you may need to set `lazy_load_plugins = True` in the Airflow config if you have a plugin that logs when loaded. | |
| .. note:: | |
| For this to work accurately, you must ensure Airflow does not log any additional text to stdout. For example, you may need to fix any deprecation warnings, or need to set ``lazy_load_plugins = True`` in the Airflow config if you have a plugin that logs when loaded. |
I think deprecation warnings log to stderr and can be avoided with 2>/dev/null though?
There was a problem hiding this comment.
Quite possible, i fixed my deprecation warnings so i don't have an easy way to test, but i can include that as a recommendation.
|
Need to fix CI failures in static checks and doc build. |
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
(cherry picked from commit 1b2b666)
6 participants
As a followup to #31655, adds an example for using the CLI list-import-errors command to test for import errors as part of a CI job, including a note about how to avoid unexpected logging that can interfere with the test.
related: #31655