Fix task logging level regression in Airflow 3.1.5 #59661
Closed
Conversation
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
The root logger level was hardcoded to INFO instead of respecting the configured logging_level setting. This caused user task code using logging.getLogger(__name__).info() to not show up in task logs unless the log level was artificially high (e.g. level 55). Changes: - Set root logger level to log_level.upper() instead of hardcoded INFO - Add tests verifying root logger respects configured log level - Add test for INFO level filtering (DEBUG messages not shown) This restores the behavior from Airflow 2.x where logger.info() worked as documented.
Arunodoy18
requested review from
amoghrajesh,
ashb and
potiuk
as code owners
Contributor
Author
|
Hey, I did some small changes regarding the issue , Please review this and in any case if there is any misconduct or error please do tell me for the follow up, Regards |
kaxil
reviewed
Dec 29, 2025
| @@ -547,7 +547,7 @@ def is_atty(): | |||
| ) | |||
| config["root"] = { | |||
| "handlers": ["default"], | |||
| "level": "INFO", | |||
| "level": log_level.upper(), | |||
Member
There was a problem hiding this comment.
This looks ok but you mention in the PR description that the logs with INFO didn't show up -- but if this is hardcoded to INFO -- the info logs should have shown.
Could you confirm please
amoghrajesh
approved these changes
Dec 30, 2025
Contributor
amoghrajesh
left a comment
amoghrajesh
left a comment
There was a problem hiding this comment.
Looks fine but could you clarify @kaxil's qn?
Member
|
@Arunodoy18 I am going to close your PRs -- Please review and test your changes with correct PR description. Using LLMs without those increase maintenance burdens and CI run time. Feel free to recreate focussed PRs following those guidelines. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The root logger level was hardcoded to INFO instead of respecting the configured logging_level setting. This caused user task code using logging.getLogger(name).info() to not show up in task logs unless the log level was artificially high (e.g. level 55).
Changes:
Set root logger level to log_level.upper() instead of hardcoded INFO
Add tests verifying root logger respects configured log level
Add test for INFO level filtering (DEBUG messages not shown)
This restores the behavior from Airflow 2.x where logger.info() worked as documented.