: Kirk Lund
Sent: Thursday, March 25, 2021 1:42 PM
To: dev@geode.apache.org
Subject: Precheckin job failed to fork JVM during compile
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fbuilds%2F17742&data=04%7C01%7Cdoevans%40vmware
https://concourse.apachegeode-ci.info/builds/17742 core dumped during
compilation of one of the modules.
I believe exit code 134 means that it failed to fork a new Java VM.
I wonder what would cause a test job to be unable to fork a process. It
seems to have forked processes for compiling all of
