[jira] [Assigned] (OOZIE-3148) Rerun Failing Tests through Maven surefire

["Attila Sasvari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Attila Sasvari reassigned OOZIE-3148:
-------------------------------------

    Assignee: Attila Sasvari

> Rerun Failing Tests through Maven surefire
> ------------------------------------------
>
>                 Key: OOZIE-3148
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3148
>             Project: Oozie
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: trunk
>            Reporter: Attila Sasvari
>            Assignee: Attila Sasvari
>            Priority: Minor
>             Fix For: 5.0.0b1
>
>         Attachments: OOZIE-3148-01.patch
>
>
> OOZIE-2817 introduced rerunning of failing test cases in pre-commit builds (changed {{bin/test-patch-20-tests}} Bash script).  
> It is no longer necessary as OOZIE-3106 upgraded surefire-plugin to 2.20.1 and since of 2.19.1 version of the maven surefire plugin it is allowed rerunning failing tests via {{-Dsurefire.rerunFailingTestsCount=2}} (see http://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html). For example, a test passed in its second run will output on the screen:
> {code}
>   Run 1: ...
>   Run 2: PASS
> Then this test will be counted as a flaky test. The build will be successful, but in the end of the summary of all tests run, the number of flaky tests will be output on the screen, for example:
>   Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Flakes: 1
> {code}
> We could introduce this mechanism and update {{bin/test-patch-20-tests}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)