waf check -- Should it always run tests?

Amar Takhar verm at darkbeer.org
Fri Nov 20 17:30:24 UTC 2015

On 2015-11-20 11:28 -0600, Daniel Poirot wrote:
> On Thu, Nov 19, 2015 at 12:37 PM, Amar Takhar <verm at darkbeer.org> wrote:
> > I can add a flag to force re-run the tests.  Running unrelated tests to the
> > changes you've made is going to generate a lot of unnecessary noise.
> Hello Amar,
> When do you think you might have a 'force' option to re-run all available tests?

hah, nice timing I was just about to email you about this.  I fixed it 

The build automatically regenerates and runs each test based on the files you 
modify now -- full depenency chain.

'waf check' will run all tests irrespective of dependency status now.  'waf 
check -v' will dump log info.

> I am new to 'waf'. I would like to submit an enhancement request - or
> request enlightenment on how to do the following:
> The Coverity tools use environment variables to enable test separation.
> In the case of 'git', for example, I call the following to run the set
> of unit test shell scripts:
> export COVERITY_TEST_SUITE=$(basename $0 .sh)
> for i in `ls t[0-9]*.sh`; do
>     echo "*** $i ***"
>     export COVERITY_TEST_NAME=$(basename $i .sh)
>     export COVERITY_TEST_SOURCE=$i
>     /bin/sh $i
> done
> The 'basename' part is optional. ;-)

Can you open a ticket for this please and I will add this.


More information about the devel mailing list