The GitHub Actions job "tests" on airflow-steward.git/improve/cancelled-and-anomaly-classification has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 4e7fda99fc3ce6ec777df4486e29cd112c261c3e / Jarek Potiuk <[email protected]> feat(pr-management-triage): exclude CANCELLED from failed_checks and broaden row 22 anomaly handling Two related changes to classify-and-act.md, both prompted by misclassifications hit during a triage sweep on apache/airflow: 1. Add a new precondition glossary entry `failed_checks` that defines the canonical "real failure" set and explicitly excludes CANCELLED, NEUTRAL/SKIPPED/STALE/STARTUP_FAILURE/ ACTION_REQUIRED, and pending checks. Cancelled contexts can pull `statusCheckRollup.state` to FAILURE without indicating the PR's head SHA is broken (typically caused by a newer push superseding the run). 2. Tighten `has_deterministic_signal`'s CI-failure leg to require `failed_checks` non-empty in addition to rollup state FAILURE. The non-empty clause naturally routes rollup-FAILURE-with- empty-`failed_checks` to row 22 (data anomaly skip) instead of cascading to the row 17 draft fallback with an empty violations comment. 3. Broaden Row 22 to cover both directions of rollup-vs-context inconsistency, and update the cross-cutting hard rule to reflect that it fires before rows 17 + 19-20. Report URL: https://github.com/apache/airflow-steward/actions/runs/25646680830 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
