Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5F0211A8F for ; Fri, 15 Aug 2014 20:05:18 +0000 (UTC) Received: (qmail 19885 invoked by uid 500); 15 Aug 2014 20:05:18 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 19860 invoked by uid 500); 15 Aug 2014 20:05:18 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 19775 invoked by uid 99); 15 Aug 2014 20:05:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Aug 2014 20:05:18 +0000 Date: Fri, 15 Aug 2014 20:05:18 +0000 (UTC) From: "Benjamin Mahler (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-1705) SubprocessTest.Status sometimes flakes out MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099021#comment-14099021 ] Benjamin Mahler commented on MESOS-1705: ---------------------------------------- This would be because we recently turned on google-logging stacktraces in the libprocess tests. Note that the test is still passing but the child process seems to have received the SIGTERM after the fork but before the exec, which is fine but produces this unfortunate stack trace. [~vinodkone] perhaps we should drop the SIGTERM stacktracing, like we do within the mesos logging initialization. > SubprocessTest.Status sometimes flakes out > ------------------------------------------ > > Key: MESOS-1705 > URL: https://issues.apache.org/jira/browse/MESOS-1705 > Project: Mesos > Issue Type: Bug > Components: build > Affects Versions: 0.20.0 > Reporter: Timothy St. Clair > Priority: Minor > Labels: build > > It's a pretty rare event, but happened more then once. > [ RUN ] SubprocessTest.Status > *** Aborted at 1408023909 (unix time) try "date -d @1408023909" if you are using GNU date *** > PC: @ 0x35700094b1 (unknown) > *** SIGTERM (@0x3e8000041d8) received by PID 16872 (TID 0x7fa9ea426780) from PID 16856; stack trace: *** > @ 0x3570435cb0 (unknown) > @ 0x35700094b1 (unknown) > @ 0x3570009d9f (unknown) > @ 0x357000e726 (unknown) > @ 0x3570015185 (unknown) > @ 0x5ead42 process::childMain() > @ 0x5ece8d std::_Function_handler<>::_M_invoke() > @ 0x5eac9c process::defaultClone() > @ 0x5ebbd4 process::subprocess() > @ 0x55a229 process::subprocess() > @ 0x55a846 process::subprocess() > @ 0x54224c SubprocessTest_Status_Test::TestBody() > @ 0x7fa9ea460323 (unknown) > @ 0x7fa9ea455b67 (unknown) > @ 0x7fa9ea455c0e (unknown) > @ 0x7fa9ea455d15 (unknown) > @ 0x7fa9ea4593a8 (unknown) > @ 0x7fa9ea459647 (unknown) > @ 0x422466 main > @ 0x3570421d65 (unknown) > @ 0x4260bd (unknown) > [ OK ] SubprocessTest.Status (153 ms) -- This message was sent by Atlassian JIRA (v6.2#6252)