Saturday 2024-05-25 09:54 UTC - `gitlab-org/gitlab-foss` broken `master` with rspec unit pg16 21/32, rspec unit pg15 21/32, rspec system pg13 7/32, rspec unit pg14 single-db-ci-connection 21/32, rspec unit pg14 single-db 21/32, rspec unit pg14 single-r...
gitlab-org/gitlab-foss pipeline #1305239699 failed
Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|
1305239699 |
master |
Add latest changes from gitlab-org/gitlab@master | N/A | schedule |
114.06 minutes |
Failed jobs (7):
-
rspec unit pg16 21/32 Job ID:
6938769922
(retry with@gitlab-bot retry_job 6938769922
) -
rspec unit pg15 21/32 Job ID:
6938769700
(retry with@gitlab-bot retry_job 6938769700
) -
rspec system pg13 7/32 Job ID:
6938769486
(retry with@gitlab-bot retry_job 6938769486
) -
rspec unit pg14 single-db-ci-connection 21/32 Job ID:
6938769072
(retry with@gitlab-bot retry_job 6938769072
) -
rspec unit pg14 single-db 21/32 Job ID:
6938769033
(retry with@gitlab-bot retry_job 6938769033
) -
rspec unit pg14 single-redis 21/32 Job ID:
6938768985
(retry with@gitlab-bot retry_job 6938768985
) -
rspec unit pg14 21/32 Job ID:
6938768938
(retry with@gitlab-bot retry_job 6938768938
)
Attribution:
-
grouppackage registry Category:Package Registry ./spec/services/packages/debian/extract_changes_metadata_service_spec.rb[1:1:3:10:1]
-
grouppackage registry Category:Package Registry ./spec/services/packages/debian/extract_changes_metadata_service_spec.rb[1:1:3:11:1]
-
grouppackage registry Category:Package Registry ./spec/services/packages/debian/extract_changes_metadata_service_spec.rb[1:1:3:12:1]
-
grouppackage registry Category:Package Registry ./spec/services/packages/debian/extract_changes_metadata_service_spec.rb[1:1:4:1]
-
groupproduct planning Category:Portfolio Management ./spec/features/boards/issue_ordering_spec.rb[1:3:1]
-
groupproduct planning Category:Portfolio Management ./spec/features/boards/issue_ordering_spec.rb[1:3:6]
This incident is attributed to grouppackage registry and posted in #g_package-registry
.
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 1305239699
. - 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.