[
https://issues.apache.org/jira/browse/BEAM-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388951#comment-17388951
]
Alex Amato commented on BEAM-12672:
-----------------------------------
One word of caution.
It might not be worth setting tests to run in parallel.
I know even today there are issues with running two tests in parallel (If they
generate the same job name, and run concurrently, they will fail on the
dataflow runner)
The workflow could not be created. Causes: (a8f47b4f3654731d): There is already
an active job named beamapp-jenkins-0728180349-027689. If you want to submit a
second job, try again by setting a different name.",
> 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
> Priority: P2
>
> 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.3.4#803005)
