Hi everyone, I'm following up on tackling post-commit tests greenness. (See beam post-commit policies <https://beam.apache.org/contribute/postcommits-policies/>)
During this week, I've assembled a list of most problematic flaky or failing tests <https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20test-failures%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>. Unfortunately, I'm relatively new to the project and lack triaging guides, so most of tickets contain only basic information. *I want to ask community help in following areas:* 1. If you know how to triage tests or the location of triage guide, please share the knowledge. You can post links here, or add pages to Confluence wiki <https://cwiki.apache.org/confluence/display/BEAM/> and share link here. 2. Please, check on the Jira test-failures <https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20test-failures%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>list and pick up tests that you might know how to fix and help with fixing those. Tickets that do not have owner now are not being worked on. I'm trying out easy mitigations for some of the failures (ie increasing timeouts), but those should not be treated as fixes. *Current status:* Items that are marked critical in the failures list tend to fail jobs in ~5-10% runs each. I contacted Anton Kedin directly and he works on fixes for couple of most problematic flakes currently. Anton, thank you for picking those up. Please, update owner and status of ticket if you start working on some test failure, this will save time for others who might also start looking into the failure. Thank you, --Mikhail Have feedback <http://go/migryz-feedback>?
