From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: Update dg-extract-results.* from gcc
Date: Wed, 25 Jul 2018 19:08:00 -0000 [thread overview]
Message-ID: <87601316fe.fsf@tromey.com> (raw)
In-Reply-To: <yddh8ku2mrc.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Fri, 20 Jul 2018 13:02:31 +0200")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> Therefore I propose to update both files from the gcc repo. The changes
Rainer> to the .sh version are trivial, just counting the number of DejaGnu
Rainer> ERROR lines, too.
Thank you for doing this. This is ok.
Rainer> * One could keep the files in toplevel contrib as in gcc, instead of
Rainer> stashing them away in gdb/testsuite.
I don't have an opinion on this one, either way is ok by me.
Rainer> * One could also copy over gcc's contrib/test_summary, used by the
Rainer> toplevel make mail-report.log to provide a nice summary of test
Rainer> results. However, this is currently hampered by the fact that for
Rainer> parallel make check the gdb.sum and gdb.log files are left in
Rainer> outputs/*/*/gdb.{sum,log} after dg-extract-results.sh has run instead
Rainer> of moving them to *.sep like gcc's gcc/Makefile.in does, so
Rainer> mail-report.log lists every failure twice.
I don't understand the "*.sep" comment - would you mind spelling it out?
Anyway, if this script is useful to you, it's fine with me if you want
to find a way to make it work. I think the outputs/** stuff can be
moved around or messed with pretty freely, though of course it is best
not to outright lose things.
Tom
next prev parent reply other threads:[~2018-07-25 19:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:02 Rainer Orth
2018-07-25 19:08 ` Tom Tromey [this message]
2018-07-26 20:54 ` Sergio Durigan Junior
2018-07-31 12:46 ` Rainer Orth
2018-07-31 12:44 ` Rainer Orth
2018-08-06 13:50 ` Rainer Orth
2018-08-07 11:52 ` Rainer Orth
2018-08-07 14:35 ` Pedro Alves
2018-08-08 14:36 ` Rainer Orth
2018-08-08 15:24 ` Pedro Alves
2018-10-01 9:36 ` dg-extract-results's bad sorting behavior (Re: Update dg-extract-results.* from gcc) Pedro Alves
2018-09-11 11:02 ` [obv] Fix dg-extract-results.sh path [Re: Update dg-extract-results.* from gcc] Jan Kratochvil
2018-09-11 11:03 ` Missing toplevel contrib/ in gdb-*.tar.xz " Jan Kratochvil
2018-09-11 11:20 ` Rainer Orth
2018-09-11 12:01 ` Joel Brobecker
2018-09-12 5:21 ` [PATCH] Add "contrib" to the list of GDB support dirs (on src-release.sh) Sergio Durigan Junior
2018-09-13 14:26 ` Tom Tromey
2018-09-13 16:35 ` Sergio Durigan Junior
2018-09-12 5:23 ` Missing toplevel contrib/ in gdb-*.tar.xz [Re: Update dg-extract-results.* from gcc] Sergio Durigan Junior
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=87601316fe.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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