From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Split up multi-exec test-cases
Date: Thu, 14 May 2020 09:32:35 -0600 [thread overview]
Message-ID: <878shu4jn0.fsf@tromey.com> (raw)
In-Reply-To: <20200514152530.GA19399@delia> (Tom de Vries's message of "Thu, 14 May 2020 17:25:31 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Fix this by turning this and similar test-cases into regular, single
Tom> executable test-cases.
Tom> This fixes 100+ FAILs with target board native-gdbserver.
I don't have any issue with splitting, however I wonder...
Tom> * gdb.base/align.exp.in: ...
... if we should have a different suffix than ".in".
To me ".in" normally implies that it's processed by configure or the like.
Could we just call these ".tcl" files? If dejagnu would ignore those,
then that would work out great.
Tom
next prev parent reply other threads:[~2020-05-14 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 15:25 Tom de Vries
2020-05-14 15:32 ` Tom Tromey [this message]
2020-05-14 16:28 ` Tom de Vries
2020-05-14 17:14 ` Pedro Alves
2020-05-15 12:51 ` [committed][gdb/testsuite] Rename *.exp.in to *.exp.tcl Tom de Vries
2020-05-14 17:04 ` [committed][gdb/testsuite] Split up multi-exec test-cases Pedro Alves
2020-05-15 14:27 ` Tom de Vries
2020-05-18 14:13 ` Pedro Alves
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=878shu4jn0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.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