Thursday 2024-05-23 15:51 UTC - `gitlab-org/gitlab` broken `master` with rspec-ee unit pg14 14/28, rspec-ee unit pg14 1/28, rspec unit pg14 17/32, rspec unit pg14 2/32
gitlab-org/gitlab pipeline #1302600273 failed
Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|
1302600273 |
master |
Merge branch '358113-move-to-beta' into 'master' | Move vue_page_breadcrumbs feature into beta | push |
59.35 minutes | Lukas 'ai-pi' Eipert |
Failed jobs (4):
-
rspec-ee unit pg14 14/28 Job ID:
6923803784
(retry with@gitlab-bot retry_job 6923803784
) -
rspec-ee unit pg14 1/28 Job ID:
6923803691
(retry with@gitlab-bot retry_job 6923803691
) -
rspec unit pg14 17/32 Job ID:
6923802763
(retry with@gitlab-bot retry_job 6923802763
) -
rspec unit pg14 2/32 Job ID:
6923802581
(retry with@gitlab-bot retry_job 6923802581
)
Attribution:
-
groupdatabase Category:Database ./ee/spec/models/embedding/application_record_spec.rb[1:1]
-
groupgeo ~"Category:Geo-replication" ./ee/spec/models/geo/tracking_base_spec.rb[1:1]
-
groupcode review Category:Code Review Workflow ./spec/graphql/resolvers/merge_requests_resolver_spec.rb[1:1:10:2:1]
-
groupproject management Category:Team Planning ./spec/models/resource_event_spec.rb[1:1]
This incident is attributed to groupdatabase and posted in #g_database
.
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 1302600273
. - 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.