Skip to content

Quarantine a flaky test

Ghost User requested to merge quarantine-flaky-tests-ee-spec-features-merge_request-code_owner_approvals_reset_after_pushing_merge_conflict_spec-rb-125 into master

The Code owner approvals reset after pushing merge conflict to source branch when the project has selective code owner removals when the first merge request has been approved and then push results in a merge conflict on a file that requires review from code owners resets code owner approvals test has either flakiness1 or flakiness2 label set, which means the number of reported failures is at or above 95 percentile, indicating unusually high failure count.

This MR quarantines the test. This is a discussion starting point to let the responsible group know about the flakiness so that they can take action:

  • accept the merge request and schedule the associated issue to improve the test
  • close the merge request in favor of another merge request to delete the test

Please follow the Flaky tests management process to help us increase master stability.

Please let us know your feedback in the dedicated issue.

Related to #448726.

This change was generated by gitlab-housekeeper using the Keeps::QuarantineFlakyTests keep.

To provide feedback on your experience with gitlab-housekeeper please comment in #442003.

Merge request reports