Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6F19A200BC7 for ; Fri, 25 Nov 2016 14:05:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6DF6F160AF6; Fri, 25 Nov 2016 13:05:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B1941160B1C for ; Fri, 25 Nov 2016 14:04:59 +0100 (CET) Received: (qmail 29591 invoked by uid 500); 25 Nov 2016 13:04:58 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 29274 invoked by uid 99); 25 Nov 2016 13:04:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Nov 2016 13:04:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8D5812C0079 for ; Fri, 25 Nov 2016 13:04:58 +0000 (UTC) Date: Fri, 25 Nov 2016 13:04:58 +0000 (UTC) From: "Alex Petrov (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-12957) Segfault shadows failures in unit tests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 25 Nov 2016 13:05:00 -0000 [ 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)