Thursday 2024-02-29 18:24 UTC - `gitlab-org/gitlab` broken `master` with rspec unit pg14 14/32
gitlab-org/gitlab pipeline #1196107048 failed
Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|
1196107048 |
master |
Merge branch 'determine-sharding-key-feature-category-application_instrumentation' into 'master' | Add sharding keys for application_instrumentation | push |
50.13 minutes | Michał Zając |
Failed jobs (1):
-
rspec unit pg14 14/32 Job ID:
6290884474
(retry with@gitlab-bot retry_job 6290884474
)
Attribution:
- missing product_group_label ~"missing feature_category label" ./spec/dot_gitlab_ci/rules_spec.rb[1:4:52:1]
This incident is attributed to infrastructure and posted in #infrastructure-lounge
.
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 1196107048
. - 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.