Tuesday 2024-01-02 05:48 UTC - `gitlab-org/gitlab` broken `master` with graphql-verify, feature-flags-usage, rubocop, haml-lint ee, haml-lint, static-verification-with-database, static-analysis 2/2, static-analysis 1/2, audit-event-types-verify, graphq...
gitlab-org/gitlab pipeline #1124150000 failed
Project | Pipeline ID | Branch | Commit | Merge request | Source | Duration | Triggered by |
---|---|---|---|---|---|---|---|
gitlab-org/gitlab | 1124150000 |
master |
Merge branch '396273-upgrade-grape' into 'master' | Upgrade grape gem | push |
11.45 minutes | Shinya Maeda |
Failed jobs (21):
-
graphql-verify Job ID:
5843952196
(retry with@gitlab-bot retry_job 5843952196
) -
feature-flags-usage Job ID:
5843952153
(retry with@gitlab-bot retry_job 5843952153
) -
rubocop Job ID:
5843952152
(retry with@gitlab-bot retry_job 5843952152
) -
haml-lint ee Job ID:
5843952151
(retry with@gitlab-bot retry_job 5843952151
) -
haml-lint Job ID:
5843952150
(retry with@gitlab-bot retry_job 5843952150
) -
static-verification-with-database Job ID:
5843952147
(retry with@gitlab-bot retry_job 5843952147
) -
static-analysis 2/2 Job ID:
5843952146
(retry with@gitlab-bot retry_job 5843952146
) -
static-analysis 1/2 Job ID:
5843952145
(retry with@gitlab-bot retry_job 5843952145
) -
audit-event-types-verify Job ID:
5843952136
(retry with@gitlab-bot retry_job 5843952136
) -
graphql-schema-dump Job ID:
5843952128
(retry with@gitlab-bot retry_job 5843952128
) -
cache gems Job ID:
5843952088
(retry with@gitlab-bot retry_job 5843952088
) -
setup-test-env Job ID:
5843952087
(retry with@gitlab-bot retry_job 5843952087
) -
compile-test-assets as-if-foss Job ID:
5843952085
(retry with@gitlab-bot retry_job 5843952085
) -
compile-test-assets Job ID:
5843952084
(retry with@gitlab-bot retry_job 5843952084
) -
compile-production-assets as-if-foss Job ID:
5843952083
(retry with@gitlab-bot retry_job 5843952083
) -
compile-production-assets Job ID:
5843952082
(retry with@gitlab-bot retry_job 5843952082
) -
cache-assets:production Job ID:
5843952081
(retry with@gitlab-bot retry_job 5843952081
) -
cache-assets:test as-if-foss Job ID:
5843952080
(retry with@gitlab-bot retry_job 5843952080
) -
cache-assets:test Job ID:
5843952079
(retry with@gitlab-bot retry_job 5843952079
) -
rails-production-server-boot-puma-cng Job ID:
5843952072
(retry with@gitlab-bot retry_job 5843952072
) -
rails-production-server-boot-puma-example Job ID:
5843952070
(retry with@gitlab-bot retry_job 5843952070
)
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.
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 jobs with
@gitlab-bot retry_pipeline 1124150000
. - If the failure looks like a broken
master
, communicate the brokenmaster
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
.
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
master
handbook 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_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.