Quarantine a flaky test

The RuboCop::BatchedBackgroundMigrationsDictionary#finalize_after returns the finalize_after timestamp of the bbm with given version 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 Engineering Productivity issue tracker.

Related to #456914 (closed).

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

To provide feedback on your experience with gitlab-housekeeper please create an issue with the label GitLab Housekeeper and consider pinging the author of this keep.

added automation:gitlab-housekeeper-authored failureflaky-test groupdatabase maintenancerefactor pipelineexpedited quarantine quarantineflaky test labels

requested review from @krasio

added 1 commit

• 6201dd48 - Quarantine a flaky test

Compare with previous version

added devopsdata stores sectioncore platform typemaintenance labels

added Category:Database label

added backend label

	3 Warnings
	dcd49d0f: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines.
	This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time.
	This merge request does not refer to an existing milestone.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@OmarQunsulGitlab (UTC+2)	@hmehra (UTC+10)
~"Backend Static Code Analysis"	Reviewer review is optional for ~"Backend Static Code Analysis"	@kkloss (UTC+2)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added automation:bot-authored label

added 7 commits

• 6201dd48...410d8ab7 - 6 commits from branch master
• 975dcf40 - Quarantine a flaky test

Compare with previous version

mentioned in merge request !163085 (merged)

Discussion is happening in !163085 (comment 2058734448).

requested review from @praba.m7n and removed review request for @krasio

added 27 commits

• 975dcf40...3dd45deb - 26 commits from branch master
• 70017e5a - Quarantine a flaky test

Compare with previous version

added 227 commits

• 70017e5a...4642f688 - 226 commits from branch master
• 4e786291 - Quarantine a flaky test

Compare with previous version

added 219 commits

• 4e786291...2e0b51ca - 218 commits from branch master
• de043887 - Quarantine a flaky test

Compare with previous version

added 244 commits

• de043887...9f16a2ae - 243 commits from branch master
• f8b5c2af - Quarantine a flaky test

Compare with previous version

added 262 commits

• f8b5c2af...4bd38c9e - 261 commits from branch master
• dcd49d0f - Quarantine a flaky test

Compare with previous version

approved this merge request

added databaseapproved label

requested review from @krasio and removed review request for @praba.m7n