From: Andrew Cagney <cagney@gnu.org>
To: fnf@ninemoons.com
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] use "verbose" for notification of not running a test
Date: Wed, 03 Dec 2003 04:01:00 -0000 [thread overview]
Message-ID: <3FCD5FFE.1040500@gnu.org> (raw)
In-Reply-To: <200312011816.hB1IGOgw030384@fred.ninemoons.com>
>> At present it prints:
>>
>> WARNING: Assembly source test -- multilibs not supported by this test.
>>
>> then skips everything. That way the fact that the test was
>> intentionally skipped is recorded in the test logs - makes comparing
>> test results easier.
>
>
> I just thought it was inconsistent with all the other places that skip
> tests due to something other than a failure in a prior test, compilation
> failure, or some other failing event. Here are some examples that have
> "skip" in their message:
>
> gdb.arch/altivec-abi.exp: verbose "Skipping altivec abi tests."
> gdb.arch/altivec-regs.exp: verbose "Skipping altivec register tests."
> gdb.arch/e500-abi.exp: verbose "Skipping e500 abi tests."
> gdb.arch/e500-regs.exp: verbose "Skipping e500 register tests."
> gdb.arch/gdb1291.exp: verbose "Skipping SH backtrace tests."
> gdb.arch/gdb1431.exp: verbose "Skipping SH backtrace tests."
> gdb.arch/i386-prologue.exp: verbose "Skipping i386 prologue tests."
> gdb.arch/i386-unwind.exp: verbose "Skipping i386 unwinder tests."
Not to worried by the above :-)
> gdb.base/a2-run.exp: verbose "Skipping a2-run.exp because of noargs."
Michael, should these be "unsupported"?
Andrew
next prev parent reply other threads:[~2003-12-03 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 22:25 Fred Fish
2003-11-29 23:29 ` Daniel Jacobowitz
2003-11-30 5:46 ` Fred Fish
2003-12-01 17:44 ` Andrew Cagney
2003-12-01 18:17 ` Fred Fish
2003-12-03 4:01 ` Andrew Cagney [this message]
2003-12-01 18:14 Michael Elizabeth Chastain
2003-12-03 3:59 ` Andrew Cagney
2003-12-03 5:05 Michael Elizabeth Chastain
2003-12-03 5:25 Michael Elizabeth Chastain
2003-12-03 16:17 ` Andrew Cagney
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=3FCD5FFE.1040500@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=fnf@ninemoons.com \
--cc=gdb-patches@sources.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