From: Tom de Vries <tdevries@suse.de>
To: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] [gdb/testsuite] Fix duplicates in gdb.fortran/array-{indices, repeat}.exp
Date: Mon, 17 Jun 2024 23:26:54 +0200 [thread overview]
Message-ID: <11de86b2-b6f5-4eee-a787-77cf0bcef437@suse.de> (raw)
In-Reply-To: <CAJVr-ENcVQbLmr4LvoFfbz5GXQX=fbaLvafHOqvmo5uA=tw_5g@mail.gmail.com>
On 6/17/24 11:00, Alexandra Petlanova Hajkova wrote:
>
>
> On Tue, Jun 11, 2024 at 3:10 PM Tom de Vries <tdevries@suse.de
> <mailto:tdevries@suse.de>> wrote:
>
> When running test-case gdb.fortran/array-indices.exp on a system without
> fortran compiler, I run into a duplicate:
> ...
> Running
> /home/vries/gdb/src/gdb/testsuite/gdb.fortran/array-indices.exp ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/array-indices.exp: array-indices.exp
> gdb compile failed, default_target_compile: Can't find gfortran.
> UNTESTED: gdb.fortran/array-indices.exp: array-indices.exp
> DUPLICATE: gdb.fortran/array-indices.exp: array-indices.exp
> ...
>
> Fix this by adding a with_test_prefix at the toplevel.
>
> Likewise in gdb.fortran/array-repeat.exp.
>
>
> Hi,
>
> I can confirm I can reproduce this issue on aarch64 and that your patch
> is fixing it
> Reviewed-By: Alexandra Petlanova Hajkova <ahajkova@redhat.com
Hi Alexandra,
thanks for the review, pushed.
Thanks,
- Tom
> <mailto:ahajkova@redhat.com>>
>
>
> make check TESTS=gdb.fortran/array-indices.exp
> BEFORE the fix:
> gdb compile failed, default_target_compile: Can't find gfortran.
> gdb compile failed, default_target_compile: Can't find gfortran.
> DUPLICATE: gdb.fortran/array-indices.exp: array-indices.exp
>
> === gdb Summary ===
>
> # of untested testcases 2
> # of duplicate test names 1
> /root/build/gdb/gdb version 16.0.50.20240612-git -nw -nx -q -iex "set
> height 0" -iex "set width 0" -data-directory /root/build/gdb/data-directory
>
> AFTER;
> Running
> /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.fortran/array-indices.exp ...
> gdb compile failed, default_target_compile: Can't find gfortran.
> gdb compile failed, default_target_compile: Can't find gfortran.
>
> === gdb Summary ===
>
> # of untested testcases 2
> /root/build/gdb/gdb version 16.0.50.20240612-git -nw -nx -q -iex "set
> height 0" -iex "set width 0" -data-directory /root/build/gdb/data-directory
>
prev parent reply other threads:[~2024-06-17 21:26 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
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 [this message]
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=11de86b2-b6f5-4eee-a787-77cf0bcef437@suse.de \
--to=tdevries@suse.de \
--cc=ahajkova@redhat.com \
--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).