Thursday 2023-07-06 10:55 UTC - `gitlab-org/gitlab` broken `master` with jest 7/12
gitlab-org/gitlab pipeline #922926384 failed
Branch: master
Commit: Merge branch 'pedropombeiro/seed-ci_running_builds' into 'master'
Triggered by Rémy Coutable • Source: push
• Duration: 122.25 minutes
Failed jobs (1):
General guidelines
Follow the Broken master
handbook guide.
Attribution
We identified the following RSpec tests failing in this incident with the corresponding groups. The group having most of the failing tests is assigned to the incident.
It can happen that we assign the wrong group this could be because of incorect or missing feature_category in the test metadata,
follow the guide to update the feature_category
.
Update the incident with the correct label.
If no group label is identified add Engineering Productivity label.
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
.
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 label, and master:broken
or master:foss-broken
label, to speed up the master
-fixing pipelines.