Wednesday 2023-07-12 09:56 UTC - `gitlab-org/gitlab` broken `master` with rspec integration pg14 8/12

gitlab-org/gitlab pipeline #928572002 failed

Branch: master

Commit: Merge branch 'sc1-release-manifest-import-hash-tag' into 'master'

Triggered by Roy Zwambag • Source: push • Duration: 86.58 minutes

Failed jobs (1):

• rspec integration pg14 8/12

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.

• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:1:6:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:2:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:2:2:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:2:3:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:3:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:3:2]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:1:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:2:1:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:2:1:2]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:2:2:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:2:2:2]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:2:2:3]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:2:3:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:1:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:2:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:3:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:4:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:5:1]
• grouppipeline execution Category:Continuous Integration ./spec/controllers/projects/settings/ci_cd_controller_spec.rb[1:1:4:3:6:1:1]

This incident is attributed to grouppipeline execution and posted in #g_pipeline-execution

Investigation

Be sure to fill the Timeline for this incident.

1. If the failure is new, and looks like a potential flaky failure, you can retry the failing job. Make sure to mention the retry in the Timeline and leave a link to the retried job.
2. If the failure looks like a broken master, communicate the broken master in Slack using the "Broadcast Master Broken" workflow:

• Click the Shortcut lightning bolt icon in the #master-broken channel and select "Broadcast Master Broken".
• Click "Continue the broadcast" after the automated message in #master-broken.

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_maintainers or #frontend_maintainers to 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.

Resolution

Follow the Resolution steps from the handbook.