[petsc-dev] limiting tests to avoid unneeded ones
Scott Kruger
kruger at txcorp.com
Thu Jan 11 10:10:39 CST 2018
On 1/11/18 5:05 AM, Jed Brown wrote:
> You'd need to know that 'master' was actually clean for that commit with
> your configuration on your machine. If an automated system, where would
> that information be stored?
>
> If not automated, just run the git diff and then make test the desired
> packages.
The dependency in the makefile is on petsc lib for every test.
To test just the desired packages, you'd have to either a) add a
search='ts%' to the gmakefile line, b) have the testing use separate
libs for the build/test cycle, c) add new functionality to make
it easier.
Scott
--
Tech-X Corporation kruger at txcorp.com
5621 Arapahoe Ave, Suite A Phone: (720) 974-1841
Boulder, CO 80303 Fax: (303) 448-7756
More information about the petsc-dev
mailing list