Thursday 2023-05-25 23:20 UTC - `gitlab-org/gitlab` broken `master` with rspec-ee system pg13 10/10, rspec-ee system pg13 9/10, rspec-ee system pg13 8/10, rspec-ee system pg13 7/10, rspec-ee system pg13 6/10, rspec-ee system pg13 5/10, rspec-ee system ...

gitlab-org/gitlab pipeline #879424168 failed

Branch: master

Commit: Merge branch '390978-fix-spec-violations-in-ee-spec-frontend-security_configuration-dast_profiles-components' into 'master'

Triggered by Jose Ivan Vargas • Source: push • Duration: 205.2 minutes

Failed jobs (27):

• rspec-ee system pg13 10/10
• rspec-ee system pg13 9/10
• rspec-ee system pg13 8/10
• rspec-ee system pg13 7/10
• rspec-ee system pg13 6/10
• rspec-ee system pg13 5/10
• rspec-ee system pg13 4/10
• rspec-ee system pg13 3/10
• rspec-ee system pg13 2/10
• rspec system pg13 25/28
• rspec system pg13 22/28
• rspec system pg13 21/28
• rspec system pg13 20/28
• rspec system pg13 19/28
• rspec system pg13 17/28
• rspec system pg13 16/28
• rspec system pg13 15/28
• rspec system pg13 14/28
• rspec system pg13 13/28
• rspec system pg13 12/28
• rspec system pg13 11/28
• rspec system pg13 10/28
• rspec system pg13 9/28
• rspec system pg13 8/28
• rspec system pg13 5/28
• rspec system pg13 4/28
• rspec system pg13 3/28

General guidelines

Follow the Broken master handbook guide.

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.