Rescues response error when fetching job trace
What does this MR do and why?
Resolves the error reported in #1526 (closed)
We may want to label such incidents with ~master-broken::e2e
or other labels to indicate that this is an e2e test failure. We can also attribute such failure to the test-platform
channel. But for now, I will focus on getting the bug resolved.
closes #1526 (closed)
Expected impact & dry-runs
Ran with this event which created gitlab-org/quality/engineering-productivity/job-timeout-incidents-playground#20 (closed)
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
-
Edited by Jennifer Li