Thursday 2022-12-01 04:55 UTC - `gitlab-org/gitlab` broken `master` with rspec-ee unit pg13 10/18, rspec-ee unit pg12 opensearch2 10/18, rspec-ee unit pg12 opensearch1 10/18, rspec-ee unit pg12 es7 10/18, rspec-ee unit pg11 10/18, rspec unit pg11 17/28...
gitlab-org/gitlab pipeline #710046322 failed
Branch: master
Commit: Merge branch 'sselhorn-master-patch-14672' into 'master'
Triggered by schedule
• Duration: 220.0 minutes
Failed jobs (8):
- rspec-ee unit pg13 10/18
- rspec-ee unit pg12 opensearch2 10/18
- rspec-ee unit pg12 opensearch1 10/18
- rspec-ee unit pg12 es7 10/18
- rspec-ee unit pg11 10/18
- rspec unit pg11 17/28
- rspec-ee unit pg12 single-db 10/18
- rspec-ee unit pg12 10/18
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
Timeline
and leave a link to the retried job. - If the failure looks like a broken
master
, communicate the brokenmaster
in Slack using the "Broadcast Master Broken" workflow:- Click the Shortcut lightning bolt icon in the
#master-broken
channel 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_maintainers
or#frontend_maintainers
to get a maintainer take a look at the fix ASAP.
In both cases, make sure to add the ~"pipeline:expedite-master-fixing" label, and master:broken
or master:foss-broken
label, to speed up the master
-fixing pipelines.