From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] [gdb/testsuite] Fix duplicates in gdb.fortran/huge.exp
Date: Thu, 20 Jun 2024 15:40:22 +0200 [thread overview]
Message-ID: <e6027499-4d66-4c7f-930e-47118093c9fb@suse.de> (raw)
In-Reply-To: <20240611131116.24494-2-tdevries@suse.de>
On 6/11/24 15:11, Tom de Vries wrote:
> With test-case gdb.fortran/huge.exp, on a system without fortran compiler, I
> ran into a number of duplicates:
> ...
> Running /home/vries/gdb/src/gdb/testsuite/gdb.fortran/huge.exp ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/huge.exp: huge.exp
> ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/huge.exp: huge.exp
> DUPLICATE: gdb.fortran/huge.exp: huge.exp
> UNSUPPORTED: gdb.fortran/huge.exp: require failed: expr $compilation_succeeded
> ...
>
> Fix this by wrapping the compile in a with_test_prefix, getting us instead:
> ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/huge.exp: CRASH_GDB=2097152: huge.exp
> ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/huge.exp: CRASH_GDB=16: huge.exp
> UNSUPPORTED: gdb.fortran/huge.exp: require failed: expr $compilation_succeeded
> ...
>
I've pushed the rest of the series (the 1st patch was already committed).
Thanks,
- Tom
> Tested on x86_64-linux.
> ---
> gdb/testsuite/gdb.fortran/huge.exp | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.fortran/huge.exp b/gdb/testsuite/gdb.fortran/huge.exp
> index 8d2158f172b..78c1d521e2a 100644
> --- a/gdb/testsuite/gdb.fortran/huge.exp
> +++ b/gdb/testsuite/gdb.fortran/huge.exp
> @@ -37,8 +37,10 @@ lappend opts f90
> set compilation_succeeded 0
> for { set size [expr $max] } { $size >= $min } { set size [expr $size / 2] } {
> set try_opts [concat $opts [list additional_flags=-DCRASH_GDB=$size]]
> - if { [build_executable $testfile.exp $testfile $srcfile $try_opts] == -1 } {
> - continue
> + with_test_prefix CRASH_GDB=$size {
> + if { [build_executable $testfile.exp $testfile $srcfile $try_opts] == -1 } {
> + continue
> + }
> }
>
> set compilation_succeeded 1
next prev parent reply other threads:[~2024-06-20 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:11 [PATCH 1/4] [gdb/testsuite] Fix duplicates in gdb.fortran/array-{indices,repeat}.exp Tom de Vries
2024-06-11 13:11 ` [PATCH 2/4] [gdb/testsuite] Fix duplicates in gdb.fortran/huge.exp Tom de Vries
2024-06-20 13:40 ` Tom de Vries [this message]
2024-06-11 13:11 ` [PATCH 3/4] [gdb/testsuite] Fix duplicates in gdb.opt/inline-cmds.exp Tom de Vries
2024-06-11 13:11 ` [PATCH 4/4] [gdb/testsuite] Fix duplicates in gdb.base/watchpoint-unaligned.exp Tom de Vries
2024-06-17 9:00 ` [PATCH 1/4] [gdb/testsuite] Fix duplicates in gdb.fortran/array-{indices, repeat}.exp Alexandra Petlanova Hajkova
2024-06-17 21:26 ` Tom de Vries
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=e6027499-4d66-4c7f-930e-47118093c9fb@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).