The GitHub Actions job "Tests (AMD)" on airflow.git/1fanwang/aip97-failure-details has failed. Run started by GitHub user 1fanwang (triggered by 1fanwang).
Head commit for run: 0de4133d8d6193d79bee18120b6dd1e932d813d2 / 1fanwang <[email protected]> AIP-97: Disruption Readiness: classify why a task failed and refund infra retries (no DB) Pillar 1: add a `failure_kind` argument (infra / application / timeout / manual) and a transient `reason` token to the `on_task_instance_failed` listener hook. The worker sets application or timeout for the failures it catches; the scheduler sets infra for a task killed from outside. The Kubernetes executor classifies a failed pod (Evicted / preempted is infra; an app crash or an OOMKill against the container's own limit is application). pluggy dispatches by name, so a listener that does not declare the arguments is unchanged. Pillar 2: a failure classified as infra gives back the retry it used (reuses `max_tries`, bounded by `[core] max_infra_refunds`), so infra churn does not spend a task's `retries`. Opt-in via `[core] infra_failure_refund_retries`, off by default. No schema change: the reason is handed to the listener at failure time rather than persisted, so this backports cleanly to older release branches with no upgrade or rollback step. How the reason token best reaches the listener (this transient `reason` argument, or folding it into the existing `error` argument) is AIP-97 open question 3. Co-authored-by: Copilot <[email protected]> Signed-off-by: 1fanwang <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/30319640967 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
