Monday 2023-07-10 16:32 UTC - `gitlab-org/gitlab` broken `master` with coverage-frontend
gitlab-org/gitlab pipeline #926575097 failed
Branch: master
Commit: Merge branch '391044-vue3-migration-ide_status_bar_spec' into 'master'
Triggered by Ezekiel Kigbo • Source: push • Duration: 58.24 minutes
Failed jobs (1):
General guidelines
Follow the Broken master handbook guide.
Attribution
If RSpec tests failed, the group having most of the failing tests is assigned to the incident.
Please note that if the assigned group is wrong, the tests may be tagged with the wrong feature_category metadata. You can follow the guide to update it so future incidents will be labelled with the correct group.
Engineering Productivity will be added if no group label is identified.
Investigation
Be sure to fill the Timeline for this incident.
- If the failure is new, and looks like a potential flaky failure, you can retry the failing job.
Make sure to mention the retry in the
Timelineand leave a link to the retried job. - If the failure looks like a broken
master, communicate the brokenmasterin Slack using the "Broadcast Master Broken" workflow:
- Click the Shortcut lightning bolt icon in the
#master-brokenchannel and select "Broadcast Master Broken". - Click "Continue the broadcast" after the automated message in
#master-broken.
Pre-resolution
If you believe that there's an easy resolution by either:
- Reverting a particular merge request.
- Making a quick fix (for example, one line or a few similar simple changes in a few lines).
You can create a merge request, assign to any available maintainer, and ping people that were involved/related to the introduction of the failure.
Additionally, a message can be posted in
#backend_maintainersor#frontend_maintainersto get a maintainer take a look at the fix ASAP.
In both cases, make sure to add the ~"pipeline:expedite" label, and master:broken or master:foss-broken label, to speed up the master-fixing pipelines.