Quarantine flaky code owner merge request tests
What does this MR do and why?
Quarantines the following flaky tests due to race condition in protected branch code owner approval propagation:
merge_with_code_owner_in_subgroup_spec.rb-
merge_with_code_owner_in_root_group_spec.rb
These tests are failing because the protected branch code owner requirement hasn't fully propagated to the MR evaluation logic when the test checks if the MR is mergeable. This is an eventual consistency issue where the assertion expect(merge_request).not_to be_mergeable fails prematurely.
The quarantine is limited to the 'ee-qa-browser_ui-3_create' job where the failures are concentrated, allowing the tests to continue running in other job contexts.
References
Relates to:
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/20565+
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/21910+
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/20644+
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/20590+
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/20546+
- https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/20512+
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.