From: Abhay Kandpal <abhay@linux.ibm.com>
To: aburgess@redhat.com
Cc: gdb-patches@sourceware.org, Ulrich.Weigand@de.ibm.com, cel@linux.ibm.com
Subject: New failures on Power9/Power10 after '**' skip glob patch
Date: Thu, 2 Apr 2026 20:07:35 +0530 [thread overview]
Message-ID: <e2bcec3e-35f2-492c-af77-50fadb6da310@linux.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4468 bytes --]
Hi Andrew,
We are observing new test failures on both Power10 and Power9 following the recent patch:
commit 5ed98c177f9a2381fe5c6ab873d05f1e5dcb8f7f
Author: Andrew Burgess<aburgess@redhat.com>
Date: Wed Feb 4 20:31:31 2026 +0000
gdb: introduce '**' for skip globs
Failure cases:
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=xxx: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=xxx: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=xxx: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=aa/bb*/file*.*c*: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=aa/bb*/file*.*c*: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=bb/*.c: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/*.c: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/**/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/**/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/**/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/ff/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/ff/*.c: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ee/ff/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=dd/**/**/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=dd/**/**/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=dd/**/**/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ROOT/aa/bb/*.c: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=true: spec=ROOT/aa/bb/*.c: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=xxx: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=xxx: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=xxx: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=aa/bb*/file*.*c*: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=aa/bb*/file*.*c*: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=bb/*.c: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/*.c: step into func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/**/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/**/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/**/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/ff/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/ff/*.c: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ee/ff/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=dd/**/**/*.c: step into func2
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=dd/**/**/*.c: skip func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=dd/**/**/*.c: skip func4
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ROOT/aa/bb/*.c: step into func3
FAIL: gdb.base/skip-tree.exp: relative_compile_filenames=false: spec=ROOT/aa/bb/*.c: step into func4
=== gdb Summary ===
# of expected passes 160
# of unexpected failures 40
Environment details:
P10 (ppc64le)
NAME="Fedora Linux"
VERSION="43 (Server Edition)"
P9 (ppc64le)
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
These failures started appearing after the above patch was applied.
Please let us know if you need additional logs or details.
Regards
Abhay Kandpal
[-- Attachment #2: Type: text/html, Size: 5579 bytes --]
next reply other threads:[~2026-04-02 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 14:37 Abhay Kandpal [this message]
2026-04-08 5:44 ` Abhay Kandpal
2026-04-16 16:22 ` Andrew Burgess
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=e2bcec3e-35f2-492c-af77-50fadb6da310@linux.ibm.com \
--to=abhay@linux.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aburgess@redhat.com \
--cc=cel@linux.ibm.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