cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-12957) Segfault shadows failures in unit tests
Date Fri, 25 Nov 2016 13:02:58 GMT
Alex Petrov created CASSANDRA-12957:

             Summary: Segfault shadows failures in unit tests
                 Key: CASSANDRA-12957
             Project: Cassandra
          Issue Type: Bug
          Components: Testing
            Reporter: Alex Petrov

It looks like a segfaulting VM will shadow the CI results, for example [here|],
I added a test that segfaults. 

Some times the tests with

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

error messages are disregarded or skipped due to the lack of information. Although if you
look closer in the [full log|]
you will see the actual segfault: 

12:51:30     [junit] # A fatal error has been detected by the Java Runtime Environment:
12:51:30     [junit] #
12:51:30     [junit] #  SIGSEGV (0xb) at pc=0x00007f7dac4b9900, pid=12587, tid=140177756509952

Test result is {{1 failure}} (which is kind of expected), but this failure resulted into skip
of all the other tests. 

Can we track the tests that were skipped not by test runner (reported by {{Failed: x, Skipped:
y}} in test results), but without "intention" (test runner crash, segfault etc) and maybe
add more infos on segfaults (possibly whole trace)? Might be there are unnoticed segfaults?

cc [~philipthompson]

This message was sent by Atlassian JIRA

View raw message