Looks like either a Surefire bug or corrupt memory. Haven't seen this before.
On Tue, Oct 20, 2015 at 6:18 PM, Matthias J. Sax <mj...@apache.org> wrote: > I never saw something like this before... Travis hick up? Can be > ignored? Or severe issues? > > https://travis-ci.org/mjsax/flink/jobs/86431071 > > -Matthias > >> # >> # A fatal error has been detected by the Java Runtime Environment: >> # >> SUREFIRE-859: # SIGSEGV (0xb) at pc=0x00007f8e02dd96b2, pid=21578, >> tid=140247046248192 >> # >> # JRE version: Java(TM) SE Runtime Environment (8.0_31-b13) (build >> 1.8.0_31-b13) >> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.31-b07 mixed mode >> linux-amd64 compressed oops) >> # Problematic frame: >> # C [libc.so.6+0x7f6b2] >> # >> SUREFIRE-859: # 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/travis/build/mjsax/flink/flink-java/hs_err_pid21578.log >> # >> SUREFIRE-859: # If you would like to submit a bug report, please visit: >> # http://bugreport.java.com/bugreport/crash.jsp >> # >> Aborted (core dumped) > > >
