Tuesday 2023-11-21 12:04 UTC - `gitlab-org/gitlab` broken `master` with rspec system pg14 10/26
gitlab-org/gitlab pipeline #1079976641 failed
| Project | Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
|---|---|---|---|---|---|---|---|
| gitlab-org/gitlab | 1079976641 |
master |
Merge branch '426803_add_sha256_support_to_project_creation' into 'master' | Add UI to support SHA256 repositories creation | push |
71.21 minutes | Marius Bobin |
Failed jobs (1):
-
rspec system pg14 10/26 Job ID:
5584699407
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.
- groupcode review Category:Code Review Workflow ./spec/features/merge_request/user_sees_merge_request_file_tree_sidebar_spec.rb[1:4:2:1:1]
This incident is attributed to groupcode review and posted in #g_create_code-review.
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 job and post a link to the retried job.
You can use the
retry_joborretry_pipelinecommands by commenting on this incident with:
| command | purpose |
|---|---|
@gitlab-bot retry_job <job_id> |
Retry a failed job. Job ID must be associated with this incident. Every job can only be retried once. |
@gitlab-bot retry_pipeline <pipeline_id> |
Retry all failed jobs in a pipeline. Pipeline ID must be the one reported in this incident. |
- If the failure looks like a broken
master, communicate the brokenmasterin Slack using the "Broadcast Master Broken" workflow:
- Click the Shortcut lightning bolt icon in the
#master-brokenchannel 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
masterhandbook 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_maintainersor#frontend_maintainersto 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.