Re: Build failed in Jenkins: Geode-release #17

A "ulimit -a" would be sufficient Le 7/28/2016 à 9:56 AM, Mark Bretl a écrit : We don't have any information, however, we could add a few shell commands at the beginning of the build to help debug possible issues that could come up? If we need anything specific, we would have to create an INFRA

Re: Build failed in Jenkins: Geode-release #17

We don't have any information, however, we could add a few shell commands at the beginning of the build to help debug possible issues that could come up? If we need anything specific, we would have to create an INFRA ticket. --Mark On Thu, Jul 28, 2016 at 8:58 AM, Bruce Schuchardt wrote: > Do

Re: Build failed in Jenkins: Geode-release #17

Do we have any information on the ulimit settings in the account running the tests? This may just be an issue with how the account is configured. Le 7/27/2016 à 9:21 AM, Kirk Lund a écrit : Looks like OutOfMemory is the cause of this failure. Do we need to increase heap size for Jenkins or is

Re: Build failed in Jenkins: Geode-release #17

Looks like OutOfMemory is the cause of this failure. Do we need to increase heap size for Jenkins or is there a way to get debug info? -Kirk On Wed, Jul 27, 2016 at 12:37 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Build failed in Jenkins: Geode-release #17

See Changes: [wmarkito] GEODE-1696 - Updating release version -- [...truncated 1019 lines...] at com.gemstone.gemfire.internal.admin.remote.AdminRegion.destroyRegion(AdminRegion.java:128)