Labels

Master broken incidents caused by db:migrate:multi-version-upgrade job, see example: gitlab-org/quality/engineering-productivity/master-broken-incidents#5982

master-broken incidents caused by merging two merge requests impacting the outcomes of the same spec, potentially resulted in delayed pipeline feedback, would have been avoided if merge train is enabled

master-broken incidents caused by MR being merged without running a new pipeline

Test data state leaked through test cases. The same as ~"flaky-test::state leak" but it's considered broken because it's almost always happening. See https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html#state-leak

master-broken incidents caused by gap in the test selection process, meaning the tests that would have caught the issue was mistakenly filtered out via MR pipeline test selection.

The cause of the failure is not straight forward and yet to be determined

Used to track broken masters and their fixes.

Used to track broken FOSS masters and their fixes.

Issues that caused "broken master" and were addressed by quarantining, reverting, or temporary workarounds.

Used to notify Mattermost Support for technical issues with GitLab Mattermost and escalation by GitLab Support

This item is part of the plan to get the associated category to the complete maturity level

This item is part of the plan to get the associated category to the lovable maturity level

This item is part of the plan to get the associated category to the minimal maturity level

This item is part of the plan to get the associated category to the planned maturity level

This item is part of the plan to get the associated category to the viable maturity level

Related to the merge request widget (merge actions, and branches, pipelines, approvals, and tests summaries)

Issues related to merge requests and code review

Issues related to the project this label is applied to, for example issue triage or labeling policies.