Friday 2022-12-23 09:35 UTC - `gitlab-org/gitlab` broken `master` with rspec-ee unit pg12 10/18, rspec-ee unit pg12 3/18, rspec unit pg12 26/28, rspec unit pg12 12/28, rspec unit pg12 4/28
gitlab-org/gitlab pipeline #730678390 failed
Branch: master
Commit: Merge branch 'add-noteable-commenters-field' into 'master'
Triggered by Alper Akgun • Source: push • Duration: 47.65 minutes
Failed jobs (5):
- rspec-ee unit pg12 10/18
- rspec-ee unit pg12 3/18
- rspec unit pg12 26/28
- rspec unit pg12 12/28
- rspec unit pg12 4/28
General guidelines
Follow the Broken master handbook guide.
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.
- Click the Shortcut lightning bolt icon in the
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.