Quarantine a flaky test
The CloudConnector::AccessDataStorageService#execute when no records exist when the valid data JSON is provided creates a new record
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 #456857 (closed).
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 (closed).