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: Fri, 07 Dec 2018 20:06:00 -0000 [thread overview]
Message-ID: <99703054-f538-0300-2d7b-83c31357f563@redhat.com> (raw)
In-Reply-To: <87o99y301i.fsf@redhat.com>
On 12/06/2018 07:52 PM, Sergio Durigan Junior wrote:
> On Thursday, December 06 2018, Pedro Franco de Carvalho wrote:
>
>> Pedro Alves <palves@redhat.com> writes:
>>
>>> Here's a quick bash POC.
>>
>> Thanks for the script! However, for the buildbots I don't have access
>> to the parallel outputs folder through the webpage (or I don't know
>> where to find them).
>>
>> Still, the merged gdb.log file seems to already have the completion
>> times, e.g.:
>>
>> testcase [...]gdb.trace/unavailable.exp completed in 28 seconds
Indeed!
>
> The results can be found at <https://gdb-build.sergiodj.net/results/>,
> but you're, you just have access to the consolidated gdb.log, not the
> different logs under output/.
Given the above, then I have to ask: what's the advantage of the
new timestamped output mode? Why not just extract the info out
of the gdb.log file? It's less code to maintain, and you don't
have to remember to run the testsuite in a special mode, nor
record stdout of the test run.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-12-07 20:06 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
2018-12-06 19:32 ` Pedro Franco de Carvalho
2018-12-06 19:52 ` Sergio Durigan Junior
2018-12-07 20:06 ` Pedro Alves [this message]
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=99703054-f538-0300-2d7b-83c31357f563@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