The Apache build from 18 March had these failures:
com.gemstone.gemfire.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
47 ms 1
com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionExecutionDUnitTest.testBug41367
11 sec 1
com.gemstone.gemfire.cache.management.MemoryThresholdsDUnitTest.testDistributedRegionClientPutRejection
https://builds.apache.org/job/Geode-nightly/412/testReport/
Le 3/18/2016 1:07 PM, Kirk Lund a écrit :
There were three dunit failures in the nightly build last night:
Test Result
<https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/1956/testReport/>
(3
failures / ±0)
-
com.gemstone.gemfire.internal.cache.tier.sockets.UpdatePropagationDUnitTest.testVerifyUpdatesReceivedByOtherClients
<https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/1956/testReport/junit/com.gemstone.gemfire.internal.cache.tier.sockets/UpdatePropagationDUnitTest/testVerifyUpdatesReceivedByOtherClients/>
-
com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionExecutionDUnitTest.testBug41367
<https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/1956/testReport/junit/com.gemstone.gemfire.internal.cache.execute/DistributedRegionFunctionExecutionDUnitTest/testBug41367/>
-
com.gemstone.gemfire.cache.management.MemoryThresholdsDUnitTest.testDistributedRegionClientPutRejection
<https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/1956/testReport/junit/com.gemstone.gemfire.cache.management/MemoryThresholdsDUnitTest/testDistributedRegionClientPutRejection/>
DistributedRegionFunctionExecutionDUnitTest.testBug41367 was caused by my
fix for GEODE-949. I followed up with filing GEODE-1112 and committed the
fix. This test is now passing again.
-Kirk
On Fri, Mar 18, 2016 at 10:05 AM, Kirk Lund <[email protected]> wrote:
Looks like most of the affected dunit tests are ones that are currently
"DISABLED" for whatever reasons :/ On one hand that's good because it means
nobodies precheckin will fail but it's bad because these tests aren't being
run.
The problem with these "tests" is that they are using String reflection to
refer to classes that I moved to a different package and somehow these
spots were missed by the refactoring tool.
-Kirk
On Fri, Mar 18, 2016 at 10:01 AM, Kirk Lund <[email protected]> wrote:
Looks like some dunit tests are failing due to the commit of GEODE-949. I
ran precheckin multiple times on feature/GEODE-949-2 before merging to
develop, so I'm not sure how this happened. I'm working on fixing up the
broken dunit tests and will commit these to develop soon.
-Kirk
