amcraig opened a new issue, #57174: URL: https://github.com/apache/airflow/issues/57174
### Apache Airflow version 3.1.0 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? Using Airflow 3.1.0 - `airflow standalone` with the LocalExecutor on MacOS 14 - M3 ARM I've noticed that occasionally tasks that are dynamically created (with `.expand()`, I don't think this is the issue fyi, just including), a subset of the them can runway, and will not fail even with a `execution_timeout` set. It completely disregards the timeout after this error is found in the logs: ``` ERROR - Received SIGSEGV signal while processing <my dag path>. source=airflow.models.dagbag.DagBag loc=dagbag.py:375 ``` Here's some screenshots from a manually failed run, note the duration of 30 minutes even though a max timeout of 3 minutes: <img width="1640" height="741" alt="Image" src="https://github.com/user-attachments/assets/a0c9b76f-fcce-4e04-aa35-e10ef6bf7072"; /> Log from the Task: <img width="1253" height="487" alt="Image" src="https://github.com/user-attachments/assets/b2782a80-71d5-4f83-b3e0-434ad5d7c03f"; /> Dag definition (linting errors are unrelated to this issue and are in a different task.): <img width="578" height="1100" alt="Image" src="https://github.com/user-attachments/assets/723bcc33-2b7a-4420-915a-463a36ef99ac"; /> --- I have a hunch this happens when the DAG Processor starts running at the same time as all of the tasks are dynamically created, but I truthfully have no clue. I don't really have an issue with tasks like this failing on standalone due to a perfect storm of conditions (and non-intended OSes) as I only use it for local testing, but I would like the tasks to not run away. --- Possibly Related Ticket: https://github.com/apache/airflow/issues/47011 https://github.com/apache/airflow/issues/55838 https://github.com/apache/airflow/issues/50303 https://github.com/apache/airflow/discussions/35967 ### What you think should happen instead? _No response_ ### How to reproduce No clue, besides try casting a wide net with many dynamically created tasks in the chance that this error bubbles up. I've included my DAG code besides my custom BoxHook in case this helps. ### Operating System MacOS 14 - M3 ARM ### Versions of Apache Airflow Providers apache-airflow-providers-google==18.0.0 apache-airflow-providers-standard==1.8.0 ### Deployment Other ### Deployment details Local Standalone ### Anything else? I think it bubbles up in the DAG run about 20% of the time. ### 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]
