From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89168 invoked by alias); 6 Dec 2018 15:30:01 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 89013 invoked by uid 89); 6 Dec 2018 15:29:59 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 06 Dec 2018 15:29:58 +0000 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E51AF3084259; Thu, 6 Dec 2018 15:29:56 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0C71F100190E; Thu, 6 Dec 2018 15:29:55 +0000 (UTC) Subject: Re: [PATCH] Implement timestamp'ed output on "make check" To: Sergio Durigan Junior , Pedro Franco de Carvalho References: <87va47ojas.fsf@linux.vnet.ibm.com> <87a7ljdaax.fsf@redhat.com> <87sgzbohzb.fsf@linux.vnet.ibm.com> <87efavbu02.fsf@redhat.com> Cc: GDB Patches From: Pedro Alves Message-ID: <7d58b34f-3082-a266-7f38-79e4f80a533c@redhat.com> Date: Thu, 06 Dec 2018 15:30:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <87efavbu02.fsf@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-12/txt/msg00069.txt.bz2 On 12/05/2018 08:26 PM, Sergio Durigan Junior wrote: > Unfortunately they haven't reached the commit which introduces the > timestamp feature, so we still don't know exactly where they're hanging. Actually we could know even without the timestamp feature -- all the testsuite/*/gdb.log files have something like: Test run by pedro on Tue Dec 4 18:15:17 2018 at the top, and ... runtest completed at Tue Dec 4 18:15:18 2018 ... at the bottom. So a simple script could extract that info and present it in a convenient way. Thanks, Pedro Alves