[ 
https://issues.apache.org/jira/browse/BEAM-12672?focusedWorklogId=761559&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-761559
 ]

ASF GitHub Bot logged work on BEAM-12672:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Apr/22 02:26
            Start Date: 25/Apr/22 02:26
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on PR #16930:
URL: https://github.com/apache/beam/pull/16930#issuecomment-1107999696

   Am I correct that there is not a clear path forward, so this path is "done"?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 761559)
    Time Spent: 21h 10m  (was: 21h)

> Update all Precommits to rerun failed tests K times.
> ----------------------------------------------------
>
>                 Key: BEAM-12672
>                 URL: https://issues.apache.org/jira/browse/BEAM-12672
>             Project: Beam
>          Issue Type: Test
>          Components: testing
>            Reporter: Alex Amato
>            Assignee: Benjamin Gonzalez
>            Priority: P2
>             Fix For: Not applicable
>
>          Time Spent: 21h 10m
>  Remaining Estimate: 0h
>
> We should configure the precommit test suites to re-run failed tests a few 
> (K) times.
> (A bonus feature would be to tag certain tests as known flakey, and run 
> multiple attempts in parallel when the test is first ran)
> The benefits of this are to:
>  * Not have flakey tests slow down PR reviews and merges.
>  * And avoiding the need to repeatedly manually rerun the precommit test with 
> a PR comment.
>  * Getting a clear signal that failed tests are due to the code in the PR
>  * Save computing resources (Rather than needing to run the entire test suite 
> every time it fails, only the failed tests will rerun).
> (Its not realistic to have 0 flakeyness, so this is desirable to improve 
> productivity, as it can take several attempts to have all the tests pass in a 
> single run).
> Note: This does not mean that we should ignore flakey tests, which are 
> sometimes indicative of bugs. We should continue to investigate those with a 
> continuous test suite.
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to