You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[autorevert] Add infra_issue AI advisor verdict (treated like not_related) (#8213)
Adds a new AI advisor verdict **`infra_issue`** alongside `garbage`,
wired through every consumer here (ClickHouse schema, autorevert lambda,
HUD). Companion prompt change: pytorch/pytorch#188042.
**Why:** a 7-day sample of `misc.autorevert_advisor_verdicts` showed
nearly all `garbage` verdicts were actually CI infrastructure failures,
and ~13 infra failures were mislabeled `not_related`. `infra_issue`
gives them one consistent home ("the environment failed, no valid
code-level signal"); `garbage` is narrowed to genuinely corrupt/invalid
signals.
**Handling:** `infra_issue` is treated like `not_related` — it blocks
the signal from autorevert (no revert), since it isn't the suspect's
fault. `garbage` keeps its 2h suppress-then-recheck window.
**Changes:** CH schema `verdict` Enum8 gains `'infra_issue' = 6`; lambda
`AdvisorVerdict.INFRA_ISSUE` + `ADVISOR_INFRA_ISSUE`, handled like
`not_related` in `_check_advisor_verdict` (+2 tests); HUD
`AdvisorVerdictType`, badge pill ("infra issue"), and `hud_renderer`
CSS.
**⚠️ Rollout order:** the live table must be ALTERed **before** the
workflow emits `infra_issue`, or ingestion drops those rows:
```sql
ALTER TABLE misc.autorevert_advisor_verdicts
MODIFY COLUMN verdict Enum8('revert'=1,'unsure'=2,'not_related'=3,'garbage'=4,'related'=5,'infra_issue'=6);
```
Order: (1) ALTER → (2) merge this PR → (3) merge pytorch/pytorch#188042.
Reads are crash-safe throughout (unknown verdict → `unsure`).
0 commit comments