gopidesupavan commented on PR #49822:
URL: https://github.com/apache/airflow/pull/49822#issuecomment-2833636145

   > Not sure it is useful:
   > 
   > See yourselves @amoghrajesh @gopidesupavan .
   > 
   > For example here: 
https://github.com/apache/airflow/actions/runs/14693388685/job/41232271080?pr=49822
   > 
   > 
![image](https://private-user-images.githubusercontent.com/595491/437970781-4c592cd9-c268-457e-97c4-7e026d086cb2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDU3ODcyNzAsIm5iZiI6MTc0NTc4Njk3MCwicGF0aCI6Ii81OTU0OTEvNDM3OTcwNzgxLTRjNTkyY2Q5LWMyNjgtNDU3ZS05N2M0LTdlMDI2ZDA4NmNiMi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwNDI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDQyN1QyMDQ5MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kZmM2ZWYxZjY1MDdjOWFkNDI0MThjZDRjNDMwNmVjYTYxOWE2YTA2ZTQxYzVjYzk3NWFlMTYyYWY1NzY2ZmVmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.GQST7TSzVCBG1McpgBcZs6hyaKLUbwGuWBL6KWThEuA)
   > 
   > We could possibly optimise it somehow, (exclude some logs etc. But I am 
not sure if it's worth it.
   > 
   > Having them in separate "step" is "good enough" thouh - as generally the 
logs will not start loading until we go to that step. Maybe in some cases where 
k8s will be failing quickly, the logs will be "small enough" to be usable with 
GitHub UI though. So I am inclined to leave it as is.
   
   Oh indeed useful to see the logs, especially apiserver, dagprocessor and 
worker. in past we have some errors like notfound but we were not able to check 
until unless download the logs and see whats going on. much more visible now, 
thanks for this @potiuk  :)


-- 
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