[
https://issues.apache.org/jira/browse/GEODE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242340#comment-15242340
]
ASF subversion and git services commented on GEODE-1161:
--------------------------------------------------------
Commit f2d5969efb410011e760399765a02d07dbe17ed7 in incubator-geode's branch
refs/heads/feature/GEODE-17-2 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f2d5969 ]
GEODE-1162: convert all CLI command DUnit tests to JUnit 4
* GEODE-1161: cleanup VM and AsyncInvocation in DUnit
* define FlakyTest JUnit category
* define SecurityTest JUnit category and apply to all security tests (probably
missed a few)
* create category test to discover JUnit behavior
> DUnit VM invocations no longer need to retry 120 times
> ------------------------------------------------------
>
> Key: GEODE-1161
> URL: https://issues.apache.org/jira/browse/GEODE-1161
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
>
> The comments and version control history shows that it was originally added
> for some RMI problems on Windows pre-2004. This would have been JDK 1.3 or
> 1.4. It seems to run cleanly now without the retry. If you are writing a new
> dunit or refactoring one and introduce a problem it takes a couple minutes to
> get the failure because it sleeps for a second between each retry.
> The class is: com.gemstone.gemfire.test.dunit.VM.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
