Segfaults in Unit Test Results on CI

[Oleksandr Petrov <ol...@gmail.com>]

Hi everyone,

Wanted to ask everyone to take extra care when you see error messages such
as:

Forked Java VM exited abnormally. Please note the time in the report
does not reflect the time until the VM exit.


in your unit test reports on cassci. When you see such a failure, please
always check the full log to see what happened to the JVM, since in the
full log output there might be more information on why JVM exited, which
may be a serious issue, for example segfault due to native memory access.

Since junit already does report it all, I just wanted to stress that if you
see such things, just take a minute to check out logs in more details. If
you already do it this way - it's great and awesome.

If you would like to see an example of such report, you can refer to this
issue <https://issues.apache.org/jira/browse/CASSANDRA-12957#>[1]

[1] https://issues.apache.org/jira/browse/CASSANDRA-12957

-- 
Alex Petrov