Quarantine a flaky test
The Ci::Runners::CreateGoogleCloudProvisioningStepsService type: "project", container: project, current_user: project_maintainer, container_owner: project_owner with saas-only feature enabled returns provisioning steps
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 #450263 (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).
Merge request reports
Activity
- A deleted user
requested review from @avonbertoldi
added typemaintenance label
added devopsverify sectionci labels
- A deleted user
added backend label
5 Warnings This MR changes code in ee/
, but its Changelog commit is missing theEE: true
trailer. Consider adding it to your Changelog commits.a3d818de: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add
the feature flagexists. Otherwise, if you think the changes here don't need
to be under a feature flag, please add the label feature flagskipped, and
add a short comment about why we skipped the feature flag.For guidance on when to use a feature flag, please see the documentation.
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 @serenafang
(UTC-5)@jpcyiza
(UTC+2)Please check reviewer's status!
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 277 commits
-
cf0c3b84...9e484572 - 276 commits from branch
master
- 0592161e - Quarantine a flaky test
-
cf0c3b84...9e484572 - 276 commits from branch
Uhmm, I'm not sure why I've been selected as a reviewer. I don't really work on/in this project; I don't think I even have merge rights. @serenafang @drew
removed review request for @avonbertoldi
added 238 commits
-
851db7ac...535d4122 - 237 commits from branch
master
- 5b2852bc - Quarantine a flaky test
-
851db7ac...535d4122 - 237 commits from branch
added 209 commits
-
67a1ecb1...a86ea688 - 208 commits from branch
master
- 74882fe5 - Quarantine a flaky test
-
67a1ecb1...a86ea688 - 208 commits from branch