jens-scheffler-bosch commented on PR #35258: URL: https://github.com/apache/airflow/pull/35258#issuecomment-1785166976
> @jens-scheffler-bosch Just curious, what other mechanish we have in place to debug the failed run? Same here. I assume we have a general contratiction / conflict between "ensure that all mess is cleaned up so that no temp traces are left behind so that worker is not running out of disk space after some time" and "I want to debug, keep all the logs please". I think the best is first hand to clean up so that worker can run stable over a long time, otherwise if we miss details of traces we need to add (e.g. by cat to stdout) to put all problems into airflow task stdout so that the (whateverr logging facility of the worker) archives the logs. What I see is that as long as an error code is not a trigger of s skip of the result, the termination log already today is added as text to the `AirflowException` which is raised if error code is returned. So I assume in current code it is not too bad. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
