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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307751#comment-16307751 ] 

Hadoop QA commented on OOZIE-3148:
----------------------------------

Testing JIRA OOZIE-3148

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:red}-1{color} the patch contains 1 line(s) with trailing spaces
.    {color:red}-1{color} the patch contains 1 line(s) longer than 132 characters
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/300/

> 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.0
>
>         Attachments: OOZIE-3148-01.patch, OOZIE-3148-02.patch, OOZIE-3148-03.patch, OOZIE-3148-04.patch, OOZIE-3148-05.patch, OOZIE-3148-06.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)