[
https://issues.apache.org/jira/browse/GEODE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861553#comment-15861553
]
ASF subversion and git services commented on GEODE-2433:
--------------------------------------------------------
Commit da91cd4018d1fa8c3e86e56875542f12d6cee9cc in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=da91cd4 ]
GEODE-2433 Backwards compatibility tests are not actually running
Modified to look for the file on the class-path instead of poking
around in the file system, and to cause tests expecting to use
the old versions to fail if the file cannot be found.
> Backwards compatibility tests are not actually running
> ------------------------------------------------------
>
> Key: GEODE-2433
> URL: https://issues.apache.org/jira/browse/GEODE-2433
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Dan Smith
> Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> We have several backwards compatibility tests checked in -
> RollingUpgradeDUnitTest
> RollingUpgrade2DUnitTest
> ClientServerMiscBCDUnitTest
> These tests are all parametered by the list of old versions to run against.
> However, it looks like the code to get the list of old versions incorrectly
> just logs a message and continues on if it can't find a file called
> geodeOldVersionClasspaths.txt. That file does not exist and is not being
> generated as far is I can tell. The entire project - geode-old-versions, is
> completely empty.
> The net effect is these tests don't actually run, because the list of
> parameters is an empty list.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
