o 1.1 release branch.
-Hitesh
From: Dan Smith
To: dev@geode.apache.org
Sent: Tuesday, February 7, 2017 1:12 PM
Subject: Re: Nightly build broken
Actually, now that I think about it GEODE-2434 was probably the cause of
these backwards compatibility test failures. The buil
Thanks Dan. Lets merge this fix into 1.1 release branch.
-Hitesh
From: Dan Smith
To: dev@geode.apache.org
Sent: Tuesday, February 7, 2017 1:12 PM
Subject: Re: Nightly build broken
Actually, now that I think about it GEODE-2434 was probably the cause of
these backwards
Actually, now that I think about it GEODE-2434 was probably the cause of
these backwards compatibility test failures. The build was generating the
geodeOldVersionClasspaths file during the configuration phase. What that
means is if you run './gradlew clean precheckin', the file gets generated
*befo
The BC tests are failing with this RuntimeException (it ends up being an
initializationError):
java.lang.RuntimeException: No older versions of Geode were found to test
against
at
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.data(ClientServerMiscBCDUnitTest.java:37)
O
Looking at some of the failures, it seems it is complaining about not
finding diskstores to delete.
On 2/7/17 12:53, Kirk Lund wrote:
Last night's nightly build is pretty horrible. 121 dunit test failures.
Cluster config accounts for 13 of them and we already have a fix for those
13 only.
Any
