Hi, There was this SIGSEGV happening in the previous run for sling-trunk-1.7 [0].
Just a wild guess if it would be similar to [1]: perhaps the process doesn't have enough java heap too? How can we increase that? (I've seen OOME on jenkins earlier actually, so I think it would be good anyway) # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf6814654, pid=1179, tid=2711087936 # # JRE version: 7.0_25-b15 # Java VM: Java HotSpot(TM) Server VM (23.25-b01 mixed mode linux-x86 ) # Problematic frame: # C [libnet.so+0x14654] _fini+0x1d0c # # 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/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/bundles/scripti ng/sightly/testing/target/oak-35596/hs_err_pid1179.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Cheers, Stefan -- [0] - https://builds.apache.org/job/sling-trunk-1.7/2667/console [1] - http://stackoverflow.com/questions/21964620/java-7-update-25-crash
