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

nkeywal commented on HBASE-4955:
--------------------------------

2.12.2 is now available, and there are some activity on surefire, so we could 
have a 2.13 "soon". I tested the snapshot version on HBase trunk, the only 
issue I found is #800.

I proposed a reasonable (imho) fix for it in surefire. It covers the case for 
forkMode=perthread (i.e. medium & large tests). I don't have a non hacky fix 
for small tests (they are on a different code path in surefire), so we will 
have either to accept output on the console for small tests either to change 
the verbose small tests to medium.

The former option would likely put us with very simple tests that we should be 
able to parallelize within a single jvm, so it's reasonable.
                
> Use the official versions of surefire & junit
> ---------------------------------------------
>
>                 Key: HBASE-4955
>                 URL: https://issues.apache.org/jira/browse/HBASE-4955
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.94.0
>         Environment: all
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>
> We currently use private versions for Surefire & JUnit since HBASE-4763.
> This JIRA traks what we need to move to official versions.
> Surefire 2.11 is just out, but, after some tests, it does not contain all 
> what we need.
> JUnit. Could be for JUnit 4.11. Issue to monitor:
> https://github.com/KentBeck/junit/issues/359: fixed in our version, no 
> feedback for an integration on trunk
> Surefire: Could be for Surefire 2.12. Issues to monitor are:
> 329 (category support): fixed, we use the official implementation from the 
> trunk
> 786 (@Category with forkMode=always): fixed, we use the official 
> implementation from the trunk
> 791 (incorrect elapsed time on test failure): fixed, we use the official 
> implementation from the trunk
> 793 (incorrect time in the XML report): Not fixed (reopen) on trunk, fixed on 
> our version.
> 760 (does not take into account the test method): fixed in trunk, not fixed 
> in our version
> 798 (print immediately the test class name): not fixed in trunk, not fixed in 
> our version
> 799 (Allow test parallelization when forkMode=always): not fixed in trunk, 
> not fixed in our version
> 800 (redirectTestOutputToFile not taken into account): not yet fix on trunk, 
> fixed on our version
> 800 & 793 are the more important to monitor, it's the only ones that are 
> fixed in our version but not on trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to