[
https://issues.apache.org/jira/browse/CASSANDRA-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-12957:
------------------------------------
Description:
It looks like a segfaulting VM will shadow the CI results, for example
[here|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/],
I added a test that segfaults (on
Some times the tests with
{code}
Forked Java VM exited abnormally. Please note the time in the report does not
reflect the time until the VM exit.
{code}
error messages are disregarded or skipped due to the lack of information.
Although if you look closer in the [full
log|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/consoleFull]
you will see the actual segfault:
{code}
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
{code}
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]
was:
It looks like a segfaulting VM will shadow the CI results, for example
[here|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/],
I added a test that segfaults.
Some times the tests with
{code}
Forked Java VM exited abnormally. Please note the time in the report does not
reflect the time until the VM exit.
{code}
error messages are disregarded or skipped due to the lack of information.
Although if you look closer in the [full
log|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/consoleFull]
you will see the actual segfault:
{code}
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
{code}
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]
> Segfault shadows failures in unit tests
> ---------------------------------------
>
> Key: CASSANDRA-12957
> URL: https://issues.apache.org/jira/browse/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|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/],
> I added a test that segfaults (on
> Some times the tests with
> {code}
> Forked Java VM exited abnormally. Please note the time in the report does not
> reflect the time until the VM exit.
> {code}
> error messages are disregarded or skipped due to the lack of information.
> Although if you look closer in the [full
> log|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12651-segfault-testall/1/consoleFull]
> you will see the actual segfault:
> {code}
> 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
> {code}
> 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
(v6.3.4#6332)
