You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/02/08 19:06:00 UTC
[jira] [Updated] (GEODE-4639) Remove Java PathFinder dependency

     [ https://issues.apache.org/jira/browse/GEODE-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Smith updated GEODE-4639:
-----------------------------
    Description: 
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.

  was:
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.

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.


> 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
>             Fix For: 1.5.0
>
>
> 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)