|
From: | Gary V. Vaughan |
Subject: | Re: Stupid question about running tests |
Date: | Mon, 27 Sep 2004 19:04:32 +0100 |
User-agent: | Mozilla Thunderbird 0.8 (Macintosh/20040913) |
Bob Friesenhahn wrote:
On Sun, 26 Sep 2004, Gary V. Vaughan wrote:If you mean a shell trace, then not that I'm aware of.The best way to do it is probably to put test -n "$DEBUG" && set -x in tests/defs.in, and then call the tests with:DEBUG=1 make check TESTS=blah.test Seems like something that would be useful to commit too...Setting VERBOSE to some value already enables some output. Maybe VERBOSE should accept certain designated values, one of which also enables shell tracing?
Sounds good. VERBOSE=debug works for me :-)Don't expend too much effort though, 'cos we're moving to Autotest shortly...
It seems that CVS libtool's current woes can largely be located/identified by enabling shell tracing.
Most definitely. Cheers, Gary. -- Gary V. Vaughan ())_. address@hidden,gnu.org} Research Scientist ( '/ http://tkd.kicks-ass.net GNU Hacker / )= http://www.gnu.org/software/libtool Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |