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 D71B1200BC6 for ; Thu, 13 Oct 2016 22:17:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D5E69160AE4; Thu, 13 Oct 2016 20:17:22 +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 12AF6160AF9 for ; Thu, 13 Oct 2016 22:17:21 +0200 (CEST) Received: (qmail 75405 invoked by uid 500); 13 Oct 2016 20:17:21 -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 74764 invoked by uid 99); 13 Oct 2016 20:17:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2016 20:17:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C51562C4C82 for ; Thu, 13 Oct 2016 20:17:20 +0000 (UTC) Date: Thu, 13 Oct 2016 20:17:20 +0000 (UTC) From: "Benjamin Bannier (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-6387) Improve reporting of parallel test runner. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 13 Oct 2016 20:17:23 -0000 [ https://issues.apache.org/jira/browse/MESOS-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-6387: ------------------------------------ Description: We should improve the logging of the parallel test runner. Improved logging seems to require some parsing of GoogleTest output, e.g., to prevent interleaving test output from concurrently executing tests. We should add a verbose mode which can print results as they arrive from shards in order to not let users wonder if tests are executing. We should also provide a way to properly unify output from different shards, e.g., report passed and failed tests in a single list instead of listing all shards separately (this e.g., makes tests from failed shards reported first harder to discover). Distinguishing reports from tests run in parallel and sequentially might be useful as well. was: We should improve the logging of the parallel test runner. Improved logging seems to require some parsing of GoogleTest output, e.g., to prevent interleaving test output from concurrently executing tests. We should add a verbose mode which can print results as they arrive from shards in order to not let users wonder if tests are executing. We should also provide a way to properly unify output from different shards, e.g., report passed and failed tests in a single list instead of listing all shards separately (this e.g., makes tests from failed shards reported first harder to discover). > Improve reporting of parallel test runner. > ------------------------------------------ > > Key: MESOS-6387 > URL: https://issues.apache.org/jira/browse/MESOS-6387 > Project: Mesos > Issue Type: Improvement > Components: test > Reporter: Benjamin Bannier > Labels: mesosphere, newbie, python > > We should improve the logging of the parallel test runner. Improved logging seems to require some parsing of GoogleTest output, e.g., to prevent interleaving test output from concurrently executing tests. > We should add a verbose mode which can print results as they arrive from shards in order to not let users wonder if tests are executing. > We should also provide a way to properly unify output from different shards, e.g., report passed and failed tests in a single list instead of listing all shards separately (this e.g., makes tests from failed shards reported first harder to discover). > Distinguishing reports from tests run in parallel and sequentially might be useful as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)