GabrielEisenbergOlympus opened a new issue, #43465:
URL: https://github.com/apache/airflow/issues/43465

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.10.1
   
   ### What happened?
   
   A dbt run concluded successfully and the logs rendered as if there was an 
error:
   
![image](https://github.com/user-attachments/assets/6312db21-848c-4b2c-bbf7-f9213d4e0cec)
   
   This likely happened because of the word "ERROR" in the logs.
   
   ### What you think should happen instead?
   
   The log should not be rendered as if there was no error
   
   ### How to reproduce
   
   Run this code on an airflow instance (in my case I used astro to reproduce 
the error seen in MWAA):
   
   ```python
   from airflow.decorators import dag, task
   from datetime import datetime
   import logging
   
   logger = logging.getLogger(__name__)
   
   # Define the basic parameters of the DAG, like schedule and start_date
   @dag(
       start_date=datetime(2024, 1, 1),
       schedule="@daily",
       catchup=False,
   )
   def error_render():
       @task(task_id="render_error")
       def log_error():
           logger.info("Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1")
   
       log_error()
   
   error_render()
   ```
   
   I obtained the following output:
   
   
![image](https://github.com/user-attachments/assets/58b4f68e-f428-481e-ac5f-3b7ac0110366)
   
   
   ### Operating System
   
   Amazon Linux 2023
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Amazon (AWS) MWAA
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to