That's what I thought as well, but the job config doesn't have any timeouts set. It should, but doesn't. Something in features is causing the spawned JVM to crash. Does it perhaps need a -Xmx setting?
John On Thu, Dec 29, 2016 at 4:10 PM P. Ottlinger <[email protected]> wrote: > Am 29.12.2016 um 21:59 schrieb John D. Ament: > > It seems that this module keeps failing. Anyone know why? > > I assume we run into a timeout as the build fails/get stuck before the > OSGi container is properly booted, but just wild guess while scanning > the logs. > > Cheers, > Phil >
