-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Description
NOTE: Remember to label this issue with "
ci: sev
"
Current Status
Status could be: preemptive, ongoing, mitigated, closed. Also tell people if they need to take action to fix it (i.e. rebase).
The following workflows are failing with Resource not accessible by integration
:
- https://github.com/pytorch/pytorch/actions/runs/16737215162/job/47378409966?pr=159820
- https://github.com/pytorch/pytorch/actions/runs/16737214399/job/47378407530?pr=159820
Error looks like
Provide some way users can tell that this SEV is causing their issue.
<snip>
, args {'name': 'pytorch', 'owner': 'pytorch', 'number': 159820} failed: [{'type': 'FORBIDDEN', 'path': ['repository', 'pullRequest', 'commits', 'nodes', 0, 'commit', 'checkSuites', 'edges', 4, 'node', 'app'], 'extensions': {'saml_failure': False}, 'locations': [{'line': 26, 'column': 7}], 'message': 'Resource not accessible by integration'}]
The following workflows are failing with Resource not accessible by integration
:
- https://github.com/pytorch/pytorch/actions/runs/16737215162/job/47378409966?pr=159820
- https://github.com/pytorch/pytorch/actions/runs/16737214399/job/47378407530?pr=159820
Seeing a large spike as of today from this graph: https://pytorchci.grafana.net/public-dashboards/cde907424c284799aacd151d97720082
Created using flambeau: https://hud.pytorch.org/flambeau/s/9dc831c1-219d-4a84-9026-282e2d5eef3b
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?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status