Monday 2024-02-05 16:45 UTC - `gitlab-org/gitlab` broken `master` with rspec system pg14 7/32
gitlab-org/gitlab pipeline #1165049133 failed
Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|
1165049133 |
master |
Merge branch '436565-increase-project-component-limit' into 'master' | Increase components per project limit | push |
53.78 minutes | Avielle Wolfe |
Failed jobs (1):
-
rspec system pg14 7/32 Job ID:
6098681477
(retry with@gitlab-bot retry_job 6098681477
)
Attribution:
- groupproject management Category:Team Planning ./spec/features/issues/user_comments_on_issue_spec.rb[1:1:2:12:1]
This incident is attributed to groupproject management and posted in #g_project-management
.
How to close this incident
- Follow the steps in the Broken
master
handbook guide to - Reminder: apply the appropriate
~master-broken:*
label to document root cause before closing the incident.
Quick Tips:
- you can retry all failing jobs with
@gitlab-bot retry_pipeline 1165049133
. - a message can be posted in
#backend_maintainers
or#frontend_maintainers
to get a maintainer take a look at the fix ASAP. - add the pipeline:expedite label, and
master:broken
ormaster:foss-broken
label, to speed up themaster
-fixing pipelines.