[
https://issues.apache.org/jira/browse/GEODE-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358693#comment-16358693
]
ASF subversion and git services commented on GEODE-4639:
--------------------------------------------------------
Commit f6a982e9e81d6253d1cfd52b94c12cd2ccc6c15c in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f6a982e ]
GEODE-4639: Removing Java PathFinder concurrency test runner
Removing the dependency on Java PathFinder for running concurrent tests.
We haven't been writing new tests with this framework and the JPF team
is not merging necessary fixes.
There is still a LoopRunner available to test for concurrency issues.
> Remove Java PathFinder dependency
> ---------------------------------
>
> Key: GEODE-4639
> URL: https://issues.apache.org/jira/browse/GEODE-4639
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We added a dependency on Java PathFinder as part of Geode-3702 .
> Unfortunately, I've been unable to get the JPF team to respond to requests to
> merge fixes to JPF that are required to get JPF to really work with Geode
> code - see
> https://groups.google.com/forum/#!topic/java-pathfinder/Yb4JtrYLQg8.
> At this point I think the best course of action is to remove JPF as a test
> framework to execute on. This does not completely remove the capability to
> write concurrency tests using the ConcurrentTestRunner, but tests will have
> to use the less deterministic LoopRunner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
