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 the other modules, so it's not a persistent problem. > Task :geode-membership:compileJava # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (methodData.cpp:1252), pid=8491, tid=0x00007f1716a78700 # fatal error: unexpected tag 32 # # JRE version: OpenJDK Runtime Environment (8.0_282-b08) (build 1.8.0_282-b08) # Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode linux-amd64 compressed oops) # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/geode/geode/geode-membership/hs_err_pid8491.log <<<snip>>> > Task :geode-membership:compileJava # # Compiler replay data is saved as: # /home/geode/geode/geode-membership/replay_pid8491.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp <<<snip>>> FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':geode-membership:compileJava'. > Compilation failed with exit code 134; see the compiler error output for details.
