Mark job traces with GRPC::ResourceExhausted as flaky
What does this MR do and why?
This makes jobs as flaky in incidents if the job trace contains GRPC::ResourceExhausted
, which has been happening every so often in master broken incidents and could just be auto-retried.
Expected impact & dry-runs
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-