Run testsuite in "distribute" script

Ian Hinder

removed comment

This should be an optional argument. I see the distribute script as the only mechanism we currently have for testing simfactory. So I want a mode of using it where I don't have to wait a long time for the Cactus portion to run. I am happy for basic checkpoint and recovery to be tested (via the basicrecover.par file). We could have an option to run the test suite instead of submitting a parameter file.

2011-08-17T09:56:54+00:00

Erik Schnetter reporter

removed comment

Since distribute also builds the Cactus source tree, running the testsuite doesn't slow things down by much. You can prevent building with --no-build (or --no-clean if you don't want to build from scratch), and you can say --no-testsuite to skip running the testsuite.

For me, distribute is not just a tool to test simfactory, but to test a complete Cactus installation. We could add a new script that calls distribute with a few specific parameters to skip everything but testing simfactory, i.e. choosing a non-standard configuration name, building quicker by not optimising, using a minimal thorn list, and not running the testsuite.

2011-08-17T12:31:07+00:00

Ian Hinder

removed comment

When I build Cactus on Datura (head node has 12 cores and we use them all) the build finishes in a few minutes (maybe 10 to 20). Running the test suite for the ET thornlist can take a couple of hours, I seem to recall. Also, you probably already have the configuration built if you want to test simfactory. But your suggestion of a --no-testsuite option would be fine with me.