Hi Akim,
* Akim Demaille wrote on Mon, Mar 30, 2009 at 09:50:59PM CEST:
> Le 29 mars 09 à 00:04, Ralf Wildenhues a écrit :
>
>> One thing that one needs to look out for is, when overriding variables
>> in recursive `make' instances is that non-GNU make don't override by
>> default unless you use `
Salut Akim,
* Akim Demaille wrote on Wed, Apr 01, 2009 at 04:53:28PM CEST:
> Le 31 mars 09 à 01:01, Ralf Wildenhues a écrit :
>> * Akim Demaille wrote on Mon, Mar 30, 2009 at 09:50:59PM CEST:
>>> Le 29 mars 09 à 00:04, Ralf Wildenhues a écrit :
This is what the 'recheck' target does, rig
Le 31 mars 09 à 01:01, Ralf Wildenhues a écrit :
Salut Ralf !
* Akim Demaille wrote on Mon, Mar 30, 2009 at 09:50:59PM CEST:
Le 29 mars 09 à 00:04, Ralf Wildenhues a écrit :
I often use
STRICT_TEST_LOGS = $(shell $(LIST_FAILED_TEST_LOGS))
which makes all failing test strict. In o
* Akim Demaille wrote on Mon, Mar 30, 2009 at 09:50:59PM CEST:
> Le 29 mars 09 à 00:04, Ralf Wildenhues a écrit :
>
>>> I often use
>>>
>>> STRICT_TEST_LOGS = $(shell $(LIST_FAILED_TEST_LOGS))
>>>
>>> which makes all failing test strict. In other words, successful
>>> tests are not rerun by "m
Le 29 mars 09 à 00:04, Ralf Wildenhues a écrit :
Hi Akim,
Hi Ralf!
Agreed. While I won't change the TESTS=foo.test semantics, we can
publish that the user can use TEST_LOGS=foo.log to limit the tests
to be
run.
Never thought about that :) Thanks.
- LAZY_TEST_SUITE is not flexible
, and can be emulated by the
user on the command line or with a script (or, for GNU make, a simple
wrapper target). Thus this patch documents such an example.
Anyway, so much for details. Here's what I'm pushing to
ad-parallel-tests.
Cheers,
Ralf
2009-03-28 Ralf Wildenhues
