This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] use "verbose" for notification of not running a test


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




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]