From: Hans-Peter Nilsson <hp@bitrange.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Remove code handling old ARM aliases from GDB
Date: Fri, 06 May 2011 03:00:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1105052104000.11385@dair.pair.com> (raw)
In-Reply-To: <20110506002328.GC2568@adacore.com>
On Thu, 5 May 2011, Joel Brobecker wrote:
> > As having introduced this, you're on the hook to investigate and
> > rectify. Another option to those I mentioned is to xfail or
> > kfailing the failing tests. Please.
>
> I've tried to understand the problem, and it seems to me that Joseph's
> position is entirely reasonable in this case. He has effectively
> introduced new tests that happen to fail in the arm-elf case, is that
> correct?
A gating test within the arm testsuite was changed from matching
xscale*-*-* to arm*-*-*, so going from never-match to
always-match which at a glance seems correct there. Except that
some of the uncovered tests fail.
The theory is that way back then, a tuple matching xscale*-*-*
enabled stuff that was disabled on arm*-*-*. (It seems this has
some bearing to reality, see sim/arm/ChangeLog). Hopefully the
tests passed at that time, so no, they're not *new* tests.
Since then, at least parts of the xscale stuff have been folded
into arm*-*, but the testsuite hasn't been updated and the tests
and/or the simulator has rotted.
My take is that when you modify stuff and there's related
breakage where there was none apparent before your change, you
should at least put a minimum of effort into checking why, and
even fix it, regardless of whether it was a just a test that
never ran before or whatever.
> If they fail on arm-elf, someone who cares about this platform
> should investigate them and determine whether to fix them, or whether
> they are a sim/gdb problem (kfail), or a problem from an external
> dependency (xfail).
I opened PR 12737.
In my autotester for the src/sim simulators for various targets,
I'm using the thumbs-up from make check from the arm-elf
testsuite as a sign that it's at least no worse off than before
for that target. Having new, old or re-discovered tests that
fail where none did before, doesn't help. And no, keeping track
of new vs. old fails is overkill in the src/sim testsuite.
brgds, H-P
next prev parent reply other threads:[~2011-05-06 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 19:01 Joseph S. Myers
2011-05-04 19:21 ` Mark Kettenis
2011-05-04 19:23 ` Pedro Alves
2011-05-04 19:24 ` Pedro Alves
2011-05-05 13:21 ` Hans-Peter Nilsson
2011-05-05 13:47 ` Hans-Peter Nilsson
2011-05-05 14:34 ` Joseph S. Myers
2011-05-05 22:11 ` Hans-Peter Nilsson
2011-05-05 22:34 ` Joseph S. Myers
2011-05-05 23:06 ` Hans-Peter Nilsson
2011-05-05 23:19 ` Joseph S. Myers
2011-05-05 23:52 ` Joseph S. Myers
2011-05-06 0:23 ` Joel Brobecker
2011-05-06 3:00 ` Hans-Peter Nilsson [this message]
[not found] ` <Pine.LNX.4.64.1105052349190.20285@digraph.polyomino.org.uk>
2011-05-09 4:53 ` Hans-Peter Nilsson
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=alpine.BSF.2.00.1105052104000.11385@dair.pair.com \
--to=hp@bitrange.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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