github.com/operator-framework/operator-lifecycle-manager@v0.30.0/doc/dev/reporting_flakes.md (about)

     1  # Reporting flakes
     2  
     3  If you are struggling to get your PR through because unrelated e2e or unit tests are randomly failing, it's likely
     4  you are being plagued by a flaky test 😱, a test that wasn't constructed as carefully as it should have been and is
     5  failing even when it should be succeeding. When this happens, check our [issues](https://github.com/operator-framework/operator-lifecycle-manager/issues) 
     6  to see if it has been filed before. Search also in the `closed issues`. If you find one, re-open it if necessary. 
     7  Otherwise, [file](https://github.com/operator-framework/operator-lifecycle-manager/issues/new) a flaky test issue.
     8  
     9  Once you have an issue link, you can disable the flaky test by adding the `[FLAKE]` tag to the test name and linking the issue in the code.
    10  
    11  Example:
    12  
    13  ```
    14      // issue: https://github.com/operator-framework/operator-lifecycle-manager/issues/2635 
    15      It("[FLAKE] updates multiple intermediates", func() {
    16  ...
    17  ```
    18  
    19  You may be asked by the reviewer to supply evidence that the test is indeed flaky and not an unfortunate side effect of
    20  your contribution. We'll endeavor to make this an easy as process as possible to merge your contribution in as quickly
    21  and safely as possible.