[
https://issues.apache.org/jira/browse/HBASE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540925#comment-13540925
]
nkeywal commented on HBASE-4955:
--------------------------------
Surefire 2.13 is nearly out. I tried it, it seems to work for us, with the
restriction mentioned above: we will have to accept some partial output on
screen or to recategorize the tests. It's anyway better to wait for the
official release and see what the other users find: we don't need to be the
first users. But 2.13 is likely the winner.
I tried again with JUnit, and here the news are not so good: we still have
errors:
{noformat}
TestServerCustomProtocol.testSingleProxy:219 null
TestMultiParallel.testFlushCommitsWithAbort:226->doTestFlushCommits:267
Server count=2, abort=true expected:<1> but was:<2>
TestAdmin.testDeleteEditUnknownColumnFamilyAndOrTable:203 null
TestReplication.setUp:180 Waited too much time for truncate
Tests in error:
TestZooKeeper.testZNodeDeletes:291 » NoAuth KeeperErrorCode = NoAuth for /l1
{noformat}
I checked the JUnit mailing lists and bug tracking, there is nothing. So it's
likely us and we will have to investigate I guess.
> 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
> Fix For: 0.96.0
>
> Attachments: 4955.v1.patch, 4955.v2.patch, 4955.v2.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
