Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement timestamp'ed output on "make check"
Date: Thu, 06 Dec 2018 15:54:00 -0000	[thread overview]
Message-ID: <5ca80f12-c329-ac40-f6a9-eb8f2b71cceb@redhat.com> (raw)
In-Reply-To: <7d58b34f-3082-a266-7f38-79e4f80a533c@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On 12/06/2018 03:29 PM, Pedro Alves wrote:
> 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.

Here's a quick bash POC.

Make sure to test in parallel mode (make check-parallel),
so that each testcase gets its own gdb.log file
and then run the script, like:

 $ cd gdb
 $ make -j8 check-parallel
 $ extract-times testsuite/outputs/ | sort -n | tail -n 10
 33 seconds for testsuite/outputs/gdb.base/whatis-ptype-typedefs/gdb.log
 35 seconds for testsuite/outputs/gdb.base/quit-live/gdb.log
 35 seconds for testsuite/outputs/gdb.base/structs/gdb.log
 37 seconds for testsuite/outputs/gdb.base/gdb-sigterm/gdb.log
 39 seconds for testsuite/outputs/gdb.threads/attach-many-short-lived-threads/gdb.log
 43 seconds for testsuite/outputs/gdb.base/multi-forks/gdb.log
 48 seconds for testsuite/outputs/gdb.linespec/cpls-ops/gdb.log
 64 seconds for testsuite/outputs/gdb.linespec/cpcompletion/gdb.log
 78 seconds for testsuite/outputs/gdb.base/break-interp/gdb.log
 149 seconds for testsuite/outputs/gdb.base/sigstep/gdb.log

(that was run against an older test dir I had handy.)

[-- Attachment #2: extract-times --]
[-- Type: text/plain, Size: 393 bytes --]

#!/bin/bash

find $1 -name "gdb.log" | \
    while read line;
    do
	#echo $line
	start=$(head -n1 $line | sed 's/Test run by .* on //g')
	end=$(tail -n1 $line | sed 's/.*completed at //g')
	#echo start=$start
	#echo end=$end
	start_sec=$(date --date="$start" '+%s')
	end_sec=$(date --date="$end" '+%s')
	duration_sec=$((end_sec - start_sec))
	echo "$duration_sec seconds for $line"
    done

  reply	other threads:[~2018-12-06 15:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 22:12 Sergio Durigan Junior
2018-11-23 14:42 ` Alan Hayward
2018-11-23 15:03 ` [PATCH v2] " Sergio Durigan Junior
2018-11-23 18:23   ` Simon Marchi
2018-11-25 16:24     ` Sergio Durigan Junior
2018-11-25 19:56       ` Simon Marchi
2018-11-25 23:23         ` Sergio Durigan Junior
2018-11-26  0:47           ` Simon Marchi
2018-11-26 16:29             ` Sergio Durigan Junior
2018-11-26 17:22               ` Simon Marchi
2018-11-26 18:48           ` Sergio Durigan Junior
2018-12-05 19:39 ` [PATCH] " Pedro Franco de Carvalho
2018-12-05 19:48   ` Sergio Durigan Junior
     [not found]     ` <87sgzbohzb.fsf@linux.vnet.ibm.com>
2018-12-05 20:26       ` Sergio Durigan Junior
2018-12-06 15:30         ` Pedro Alves
2018-12-06 15:54           ` Pedro Alves [this message]
2018-12-06 19:32             ` Pedro Franco de Carvalho
2018-12-06 19:52               ` Sergio Durigan Junior
2018-12-07 20:06                 ` Pedro Alves
2018-12-07 22:09                   ` Sergio Durigan Junior
2018-12-08 12:58                     ` Pedro Alves
2018-12-08 23:16                       ` Sergio Durigan Junior
2018-12-09  8:57                         ` Philippe Waroquiers
2018-12-06 19:41         ` Pedro Franco de Carvalho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ca80f12-c329-ac40-f6a9-eb8f2b71cceb@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedromfc@linux.ibm.com \
    --cc=sergiodj@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox