pytorch/ci-sev.md at f7a13a6dfcef575bef0eaa4ddaf37d2dc337c832

mirror of https://github.com/pytorch/pytorch.git synced 2025-10-20 12:54:11 +08:00

Files

Jean Schmidt 1ec0755a7e [ISSUES] Update ci:sev template to include a note about ci: disable-autorevert label (#165459 )

We noticed that disabling autorevert in any and all ci:sevs is too impactful, as ci: sevs are sometimes created just to communicate an action or a impactful change. But sometimes durring a SEV we might not want to disable autorevert anyways, a example is a ci: sev impacting jobs we don't use as basis for autorevert.

So, a note is added reminding the ci:sev author to optionally add this tag to disable auto-revert

Note: using this opportunity to fix the ci: disable-autorevert issues. As it is best for the title to be simple and the displayed message in the GitHub interface to be decorated with emoji :)
Pull Request resolved: https://github.com/pytorch/pytorch/pull/165459
Approved by: https://github.com/malfet

2025-10-14 20:32:46 +00:00

992 B

Raw Blame History

name, about, title, labels, assignees

name	about	title	labels	assignees
⚠️ CI SEV	Tracking incidents for PyTorch's CI infra.

NOTE: Remember to label this issue with "ci: sev" If you want autorevert to be disabled, keep the ci: disable-autorevert label

Current Status

Status could be: preemptive, ongoing, mitigated, closed. Also tell people if they need to take action to fix it (i.e. rebase).

Error looks like

Provide some way users can tell that this SEV is causing their issue.

Incident timeline (all times pacific)

Include when the incident began, when it was detected, mitigated, root caused, and finally closed.

User impact

How does this affect users of PyTorch CI?

Root cause

What was the root cause of this issue?

Mitigation

How did we mitigate the issue?

Prevention/followups

How do we prevent issues like this in the future?

992 B Raw Blame History