Bruno Haible <br...@clisp.org> writes: > Ralf Wildenhues wrote: >> > However, in general, tests might be executable programs, or >> > they might be shell or other scripts. In the latter cases, putting >> > valgrind in TESTS_ENVIRONMENT would be at least a waste (you don't want >> > to check bash or perl). > > Not only it's a waste. It also produces lots of stderr output that the > developer does not want to see.
No it doesn't, my patch invokes valgrind with -q so that it does not output anything, unless there are errors, of course, but then output can be useful. /Simon
