From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: Aditya Kamath <Aditya.Kamath1@ibm.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
Aditya Vidyadhar Kamath <akamath996@gmail.com>,
"tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH v5 1/4] Remove stale legacy code from rs6000-aix-nat.c file.
Date: Wed, 14 Oct 2026 10:44:21 +0000 [thread overview]
Message-ID: <382c91d2eb16a2e2749e77f6c71b4348c7331d9e.camel@de.ibm.com> (raw)
In-Reply-To: <DSWPR15MB3198172F6E0E5D22B57AB8E8E1D69D2@DSWPR15MB319817.namprd15.prod.outlook.com>
Aditya Kamath <Aditya.Kamath1@ibm.com> wrote:
> 32-bit
> before after after + your
patches
> expected passes 41687 41541 41640
> unexpected failures 2302 2294 2308
> unexpected successes 1 1 1
> expected failures 15 15 15
> known failures 30 30 30
> unresolved testcases 11 86 11
> untested testcases 107 107 108
> unsupported tests 179 179 178
That looks better, thanks! It is still surprising to see
the differences in untested vs. unsupported tests - do you
know what this is about?
Also it is slightly concerning to see the increase in
unexpected failures - is this caused by different sets
of tests being run, or just noise?
Bye,
Ulrich
next prev parent reply other threads:[~2026-10-14 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:19 Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 2/4] Remove obsolete getthrds and HAVE_PTRACE64 configure checks Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 3/4] Modernise aix-thread.c by combining ptrace wrappers Aditya Vidyadhar Kamath
2026-10-13 11:19 ` [PATCH v5 4/4] Fix 32-bit GPR and SPR register reads/writes in pthdb callbacks Aditya Vidyadhar Kamath
2026-10-13 12:00 ` [PATCH v5 1/4] Remove stale legacy code from rs6000-aix-nat.c file Ulrich Weigand
2026-10-13 12:55 ` Aditya Kamath
2026-10-13 13:31 ` Ulrich Weigand
2026-10-13 17:16 ` Simon Marchi
2026-10-14 9:15 ` Aditya Kamath
2026-10-14 10:44 ` Ulrich Weigand [this message]
2026-10-15 13:38 ` Aditya Kamath
2026-10-15 14:37 ` Ulrich Weigand
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=382c91d2eb16a2e2749e77f6c71b4348c7331d9e.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.com \
/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