master-broken incidents mistakenly label as master-broken::infrastructure when `500 Internal Server Error` appears in the rspec trace
We have a test in https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/lib/gitlab/ci/pipeline/chain/validate/external_spec.rb?ref_type=heads#L315 which includes 500 Internal Server Error
in the spec. Because this test appeared in the failing job of a master broken incident, eventhough the failure is coming from rspec, gitlab-bot still thinks that the root cause was master-brokeninfrastructure so it labeled it incorrectly.
Edited by Jennifer Li