diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 18:07:42 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 18:07:42 +0000 |
| commit | 7b52c7cb634ef7047d30b0337fe477bcdcedf41d (patch) | |
| tree | 374ca9e908204488422046f10e340d1500780362 /doc/development/testing_guide | |
| parent | b375c6c05fbd03aea33a9ee9f82e678bdaa8c3cc (diff) | |
| download | gitlab-ce-7b52c7cb634ef7047d30b0337fe477bcdcedf41d.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/testing_guide')
| -rw-r--r-- | doc/development/testing_guide/flaky_tests.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/development/testing_guide/flaky_tests.md b/doc/development/testing_guide/flaky_tests.md index f39151cfa59..ef8676ddf32 100644 --- a/doc/development/testing_guide/flaky_tests.md +++ b/doc/development/testing_guide/flaky_tests.md @@ -44,9 +44,8 @@ On our CI, we use [rspec-retry] to automatically retry a failing example a few times (see [`spec/spec_helper.rb`] for the precise retries count). We also use a home-made `RspecFlaky::Listener` listener which records flaky -examples in a JSON report file on `master` (`retrieve-tests-metadata` and `update-tests-metadata` jobs), and warns when a new flaky example -is detected in any other branch (`flaky-examples-check` job). In the future, the -`flaky-examples-check` job will not be allowed to fail. +examples in a JSON report file on `master` (`retrieve-tests-metadata` and +`update-tests-metadata` jobs). This was originally implemented in: <https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/13021>. |