Wednesday 2023-12-13 05:18 UTC - `gitlab-org/gitlab` broken `master` with rspec integration pg15 1/12, rspec unit pg14 11/24, rspec unit pg14 8/24, rspec unit pg14 4/24, rspec unit pg14 1/24
gitlab-org/gitlab pipeline #1104834288 failed
Project | Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|---|
gitlab-org/gitlab | 1104834288 |
master |
Merge branch 'overdue-finalize-background-migration--mark-duplicate-npm-packages-for-destruction' into 'master' | Finalize migration MarkDuplicateNpmPackagesForDestruction | schedule |
242.25 minutes |
Failed jobs (5):
-
rspec integration pg15 1/12 Job ID:
5739010588
(retry with@gitlab-bot retry_job 5739010588
) -
rspec unit pg14 11/24 Job ID:
5739009431
(retry with@gitlab-bot retry_job 5739009431
) -
rspec unit pg14 8/24 Job ID:
5739009426
(retry with@gitlab-bot retry_job 5739009426
) -
rspec unit pg14 4/24 Job ID:
5739009420
(retry with@gitlab-bot retry_job 5739009420
) -
rspec unit pg14 1/24 Job ID:
5739009415
(retry with@gitlab-bot retry_job 5739009415
)
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
Please capture your investigation steps in the Investigation Steps
thread.
- If the failure is new, and looks like a potential flaky failure, you can retry the failing jobs with
@gitlab-bot retry_pipeline 1104834288
. - 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
.
Root Cause Analysis
- It is important to categorize the incident by its root cause to identify corrective actions and to track data for furture references.
- Root cause labels can be found in the Broken
master
handbook guide. Search forPlease set the appropriate ~master-broken:* label from the list below
.
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.