From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Fix setting of VSX registers
Date: Wed, 28 Jul 2010 21:43:00 -0000 [thread overview]
Message-ID: <20100728214252.GY13267@adacore.com> (raw)
In-Reply-To: <m3ocdrl2a1.fsf@fleche.redhat.com>
> One approach would be to refactor these procs so that your use can work.
> I think this would be nice to have -- I think it would be good to have
> fewer boilerplate tests with "synthetic" names, ones that nobody is
> interested in.
When we discussed the new gdb-testsuite that AdaCore uses, we talked
about that quite a bit. And unsurprisingly, there was no obvious answer.
These tests can be an annoyance if all hell breaks lose and they all
start to fail. A PASS indeed adds little value to the results. But
on the other hand, I have always felt that we should verify that these
commands have the expected results, and that we should get a FAIL if
we detect something went wrong. Ideally, we wanted to be able to group
a sequence of commands as one "setup phase" and generate one FAIL if
part of the sequence fails. But in the end, we decided that it was just
simpler to treat everything as a test (this is what I have pretty much
done in dejagnu as well).
--
Joel
next prev parent reply other threads:[~2010-07-28 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 18:59 Thiago Jung Bauermann
2010-07-22 16:06 ` Tom Tromey
2010-07-26 17:31 ` Thiago Jung Bauermann
2010-07-27 15:20 ` Joel Brobecker
2010-07-27 16:14 ` Thiago Jung Bauermann
2010-07-28 21:34 ` Tom Tromey
2010-07-28 21:43 ` Joel Brobecker [this message]
2010-07-28 21:57 ` Tom Tromey
2010-08-18 21:18 ` Thiago Jung Bauermann
2010-08-19 9:50 ` Joel Brobecker
2010-08-19 17:56 ` Thiago Jung Bauermann
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=20100728214252.GY13267@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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