This stuff in geode-assembly/build.gradle configures tests that run in the 
assembly subproject:

test {
  // test from the actual classpath not the gradle classpath
  dependsOn installDist
  // @TODO: this doesn't seem to be working need to get basename first.
  classpath += files 
"$buildDir/install/${distributions.main.baseName}/lib/geode-dependencies.jar"
}

tasks.withType(Test){
  environment 'GEMFIRE', "$buildDir/install/${distributions.main.baseName}/lib”
}


There might be a gradle configuration ordering issue here…?

Anthony


> On Jul 26, 2016, at 1:19 PM, Kirk Lund <kl...@pivotal.io> wrote:
> 
> I don't know how to fix it. I would expect :geode-assembly:flakyTest to
> look similar to :geode-assembly:distributedTest.
> 
> -Kirk
> 
> 
> On Tue, Jul 26, 2016 at 10:19 AM, Bruce Schuchardt <bschucha...@pivotal.io>
> wrote:
> 
>> It looks like the flakyTest target isn't configured to run Rest API
>> tests.  Does anyone know how to fix this?
>> 
>> 
>> Le 7/26/2016 à 7:31 AM, Apache Jenkins Server a écrit :
>> 
>>> :geode-assembly:flakyTest
>>> 
>>> com.gemstone.gemfire.rest.internal.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest
>>>> testFunctionExecutionOnAllMembers FAILED
>>>     java.lang.AssertionError: unable to locate geode-web-api WAR file
>>> 
>>>     java.lang.NullPointerException
>>> 
>> 
>> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to