accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2781) Unit tests should reuse forks by default
Date Sat, 10 May 2014 22:12:39 GMT

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

Sean Busbey commented on ACCUMULO-2781:
---------------------------------------

Just a note of clarification on keeping ITs independent: the static handling of zookeeper
caching (i.e. in fate.ZooSession) requires us to have the ITs in different JVMs. Once anyone
calls ZooSession.shutdown(), all future attempts to use that JVM will fail.

I *think* all of our unit tests don't make use of the ZooSession facilities, but it's worth
a quick check by whomever handles implementing this change.

> Unit tests should reuse forks by default
> ----------------------------------------
>
>                 Key: ACCUMULO-2781
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2781
>             Project: Accumulo
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.6.0
>            Reporter: Christopher Tubbs
>             Fix For: 1.6.1, 1.7.0
>
>
> The default value for maven-surefire-plugin's reuseForks is true. This is set to false
in our pom.xml in order to keep ITs independent. This inadvertently affects unit tests also,
and causes unit tests to create a new JVM for each test class.
> These should be separated, and the default for unit tests (maven-surefire-plugin's execution)
should be {{reuseForks=true}}, and the default for ITs (maven-failsafe-plugin's execution)
should be {{reuseForks=false}} (as it is now).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message