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
The number of force merges is on the raise recently and it's proportional to the increase in red trunk commits. In addition, we also had a CI sev in Feb where viable/strict wasn't updated for 5+ days pytorch/pytorch#120368. In both cases, handling broken trunk failures wasn't done in a timely manner. There are also some CI jobs where oncall might feel reluctant to revert right away without checking with the owner, for example rocm and inductor jobs.
The proposal here is to let the bot do it instead:
The bot will post a comment if it considers a commit is breaking trunk and should be reverted. It's cc the author and PyTorch Dev Infra (oncall)
Otherwise, after waiting for X hours, the bot will revert the change
[Optional] If the revert doesn't help and similar failures still occur in trunk, the bot could reland the reverted change providing that the necessary approval is still there.
The number of force merges is on the raise recently and it's proportional to the increase in red trunk commits. In addition, we also had a CI sev in Feb where viable/strict wasn't updated for 5+ days pytorch/pytorch#120368. In both cases, handling broken trunk failures wasn't done in a timely manner. There are also some CI jobs where oncall might feel reluctant to revert right away without checking with the owner, for example
rocm
andinductor
jobs.The proposal here is to let the bot do it instead:
cc @clee2000 @kit1980 @PaliC @malfet @seemethere
The text was updated successfully, but these errors were encountered: