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 complete maturity level

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

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

Used to track broken FOSS masters and their fixes.

Used to track broken masters and their fixes.

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

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.

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

When master pipeline incident occurs due to the runner having no disk space left.

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

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

This label is to identify master broken incidents caused by job timing out

master-broken incidents caused by various infrastructure issue such as network error, runner memory limit reached, etc.

This label describes a broken master scenario with the error "Gitlab is unable to handle this request due to load."

This label is for master broken incidents occured because gitaly is failed to setup. See example: gitlab-org/quality/engineering-productivity/master-broken-incidents#625

master-broken incidents occurred in fork repos, main FOSS and JiHu, due to code changes to the Gitlab main repo that does not have any test coverage for running in a fork repo.

master-broken incidents caused by flaky tests

This label represents a broken master pipeline caused by failing to pull docker image from the image registry.

This is to indicate master broken incidents caused by external dependency issues such as npm registry down, RubyGems.org down, etc.