Add code coverage to nightly test

[jacobmerson]

This functionality is pulled over from my implementation in
tobinw/biotissue. Valgrind is used to do memory checking, and gcov is
used for coverage.

closes #60

Note: I don't have an easy way to verify that this works. @seegyoung (I think you are in charge of the nightly tests) should try running this with ctest --script nightly.cmake. If all goes well the memory checking and test coverage should show up on cdash site.

[cwsmith]

@timetravellers we have valgrind support that works with mpirun:

core/test/testing.cmake

Lines 5 to 8 in ecc64db

	add_test(
	NAME ${TESTNAME}
	COMMAND ${MPIRUN} ${MPIRUN_PROCFLAG} ${PROCS} ${VALGRIND} ${VALGRIND_ARGS} ${EXE} ${ARGN}
	)

core/CMakeLists.txt

Lines 61 to 64 in a6b4cbf

	set(VALGRIND "" CACHE string
	"the valgrind executable")
	set(VALGRIND_ARGS "" CACHE string
	"the command line arguments to VALGRIND")

IIRC, the builtin cmake valgrind integration does not support being called by mpirun.

The gcov addition is interesting. I'll check that out. Does this address Dan's point about aggregate coverage?

I'm currently the nightly build maintainer.

[jacobmerson]

Valgrind seems to work with mpi and cdash . You can see the result of a dynamic analysis on my project here:
https://my.cdash.org/index.php?project=Biotissue&subproject=develop

As far as I know this does aggregate data as Dan was hoping for. The following project shows an example with coverage turned on (and working): https://open.cdash.org/index.php?project=CMake

On tobinw/biotissue and tobinw/amsi I had to turn off the code coverage because our codebase is not currently completely open (we include some Simmetrix calls).