From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement timestamp'ed output on "make check"
Date: Fri, 07 Dec 2018 22:09:00 -0000 [thread overview]
Message-ID: <87y391xa44.fsf@redhat.com> (raw)
In-Reply-To: <99703054-f538-0300-2d7b-83c31357f563@redhat.com> (Pedro Alves's message of "Fri, 7 Dec 2018 20:05:55 +0000")
On Friday, December 07 2018, Pedro Alves wrote:
> On 12/06/2018 07:52 PM, Sergio Durigan Junior wrote:
>> 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.
When I was writing the timestamp script, I didn't think about extracting
the info from gdb.log. So there's that. I agree that it's easier to
have the consolidated info at the end, and I can propose a patch for
that based on your shell script, but I also think it makes sense to have
the special "timestamp'd" mode, because sometimes (when a build takes
more than 120 hours, for example, which was happening until recently
with the ppc64le builders) it's useful to have the information on the
screen without having to wait, I think.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-12-07 22:09 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
2018-12-07 22:09 ` Sergio Durigan Junior [this message]
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=87y391xa44.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pedromfc@linux.ibm.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