>> de-core/build/resources/test:/poland1/users/hiteshk/work/
>> geode/release110/gemfire/open/geode-core/build/generated-
>> resources/main:/poland1/users/hiteshk/work/geode/release110/
>> gemfire/open/geode-core/build/libs/geode-core-1.1.0.jar:
>>
>>
>&g
rs/hiteshk/work/geode/release110/gemfire/open/geode-core/build/generated-resources/main:/poland1/users/hiteshk/work/geode/release110/gemfire/open/geode-core/build/libs/geode-core-1.1.0.jar:
From: Kirk Lund
To: geode
Sent: Monday, January 30, 2017 1:09 PM
Subject: Re: Build failed in
.jar:
From: Kirk Lund
To: geode
Sent: Monday, January 30, 2017 1:09 PM
Subject: Re: Build failed in Jenkins: Geode-release #39
Seems to always be from line 220:
Caused by: java.lang.RuntimeException: VMs did not start up within 120
seconds
at
Seems to always be from line 220:
Caused by: java.lang.RuntimeException: VMs did not start up within 120
seconds
at
org.apache.geode.test.dunit.standalone.DUnitLauncher.launch(DUnitLauncher.java:220)
at
org.apache.geode.test.dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:142)
...
I created GEODE-2386 for these "Unable to launch dunit VMs" failures. It
looks like this may actually be a gradle bug. I wonder if the some of the
changes for the backwards compatibility test framework somehow made it more
likely for us to hit this bug, because we're seeing it frequently now.
-Dan
