From: Fred Fish <fnf@public.ninemoons.com>
To: cagney@gnu.org (Andrew Cagney)
Cc: fnf@ninemoons.com, drow@mvista.com (Daniel Jacobowitz),
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] use "verbose" for notification of not running a test
Date: Mon, 01 Dec 2003 18:17:00 -0000 [thread overview]
Message-ID: <200312011816.hB1IGOgw030384@fred.ninemoons.com> (raw)
In-Reply-To: <3FCB7DE9.2030607@gnu.org> from "Andrew Cagney" at Dec 01, 2003 12:44:09 PM
> 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."
gdb.base/a2-run.exp: verbose "Skipping a2-run.exp because of noargs."
gdb.base/commands.exp: verbose "Skipping progvar_simple_if_test because of noargs."
gdb.base/commands.exp: verbose "Skipping progvar_simple_while_test because of noargs."
gdb.base/commands.exp: verbose "Skipping progvar_simple_if_while_test because of noargs."
gdb.base/commands.exp: verbose "Skipping if_while_breakpoint_command_test because of noargs."
gdb.base/commands.exp: verbose "Skipping infrun_breakpoint_command_test because of noargs."
gdb.base/commands.exp: verbose "Skipping breakpoint_command_test because of noargs."
gdb.base/commands.exp: verbose "Skipping watchpoint_command_test because of noargs."
gdb.base/commands.exp: verbose "Skipping test_command_prompt_position because of noargs."
gdb.base/commands.exp: verbose "Skipping bp_deleted_in_command_test because of noargs."
gdb.base/commands.exp: verbose "Skipping temporary_breakpoint_commands because of noargs."
gdb.base/fileio.exp: verbose "Skipping fileio.exp because of no fileio capabilities."
gdb.base/interrupt.exp: verbose "Skipping interrupt.exp because of nointerrupts."
gdb.base/interrupt.exp: verbose "Skipping interrupt.exp because of noinferiorio."
gdb.base/overlays.exp: verbose "Skipping overlay test -- not implemented for this target."
gdb.base/shreloc.exp: verbose "test skipped - shared object files not supported by this target."
gdb.base/sigall.exp: verbose "Skipping sigall.exp because of nosignals."
gdb.base/signals.exp: verbose "Skipping signals.exp because of nosignals."
gdb.gdbtk/cpp_variable.exp: verbose "No C++ support -- skipping test"
gdb.mi/mi2-syn-frame.exp: verbose "Skipping mi-syn-frame.exp because of nosignals."
gdb.mi/mi-syn-frame.exp: verbose "Skipping mi-syn-frame.exp because of nosignals."
-Fred
next prev parent reply other threads:[~2003-12-01 18:17 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 [this message]
2003-12-03 4:01 ` Andrew Cagney
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=200312011816.hB1IGOgw030384@fred.ninemoons.com \
--to=fnf@public.ninemoons.com \
--cc=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