[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: valgrind-tests.m4
From: |
Ralf Wildenhues |
Subject: |
Re: valgrind-tests.m4 |
Date: |
Mon, 17 May 2010 19:28:24 +0200 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
Hi Simon,
* Simon Josefsson wrote on Mon, May 17, 2010 at 12:15:51PM CEST:
> I'm running self-tests under valgrind in several projects, and it seems
> like a general useful thing, so how about putting the macro for this in
> gnulib?
Nice idea. 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). With Automake 1.11's parallel-tests option, you
have the possibility to specify per-extension "compilers" for tests.
Example:
# .sh and .pl files are processed to .log files.
TEST_EXTENSIONS = .sh .pl
SH_LOG_COMPILER = bash -vx
PL_LOG_COMPILER = perl -w -m strict
TESTS = foo.sh bar.pl baz.sh
Besides, TESTS_ENVIRONMENT really is meant as a variable for the
end-user rather than for the developer.
It would be nice to have an approach that supports these use cases (in
addition to Ben's remarks).
Cheers,
Ralf
- valgrind-tests.m4, Simon Josefsson, 2010/05/17
- Re: valgrind-tests.m4,
Ralf Wildenhues <=
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/17
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/17
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/18
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/19
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/19
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/20
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/20
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/20
- Re: valgrind-tests.m4, Bruno Haible, 2010/05/18
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/18