The GitHub Actions job "Scheduled verify release calendar" on airflow.git/main has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: dc0e0bb084d685e2cb475e312f729fbb2a262efa / Victory <[email protected]> Add on_kill() to DatabricksTaskBaseOperator to cancel runs on task kill (#69442) DatabricksSubmitRunOperator and DatabricksRunNowOperator both implement on_kill() to cancel the Databricks run when an Airflow task is killed (SIGTERM or execution_timeout). DatabricksTaskBaseOperator — the base for DatabricksTaskOperator and DatabricksNotebookOperator — was missing the same implementation, leaving Databricks jobs running after the Airflow task was killed and orphaning compute resources. DatabricksWorkflowTaskGroup received on_kill() in #42115; this PR closes the remaining gap for standalone task operators. For workflow members self.databricks_run_id is the shared parent run ID; cancelling it would stop all sibling tasks. on_kill() therefore calls _get_current_databricks_task()["run_id"] to target only the current task's own child run, mirroring monitor_databricks_job. Standalone operators continue to cancel via self.databricks_run_id directly. If resolving the child run_id fails (API error, task_key mismatch), on_kill logs the exception and returns without cancelling anything — falling back to the parent run_id would stop sibling tasks, defeating the purpose. Unit tests cover: cancel called for standalone operator, no-op when databricks_run_id is None, workflow-member cancels child run (parent=1, child=999, asserts cancel_run(999)), and workflow-member where _get_current_databricks_task raises asserts cancel_run not called. Report URL: https://github.com/apache/airflow/actions/runs/31078823011 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
