Re: Travis Error Java 8

2015-10-20 Thread Maximilian Michels
Yes, the G1 core dumps quite often for streaming users. Seems to be too buggy as a default GC. On Tue, Oct 20, 2015 at 6:30 PM, Stephan Ewen wrote: > Looks like a JVM bug. > > BTW: We may want to downgrade from G1 as the default GC in streaming mode > to CMS. In the current Java 8 versions, G1 is

Re: Travis Error Java 8

2015-10-20 Thread Stephan Ewen
Looks like a JVM bug. BTW: We may want to downgrade from G1 as the default GC in streaming mode to CMS. In the current Java 8 versions, G1 is still causing core dumps once in a while... Stephan On Tue, Oct 20, 2015 at 6:23 PM, Maximilian Michels wrote: > Looks like either a Surefire bug or co

Re: Travis Error Java 8

2015-10-20 Thread Maximilian Michels
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 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 >

Travis Error Java 8

2015-10-20 Thread Matthias J. Sax
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=0x7f8e02dd96b2, pid=21578,