Hey list, Parallel builds work fine for my build tree of a system daemon I am developing. I have unit tests in the form of check_SCRIPTS and check_PROGRAMS.
These unit tests, however, can only be partially parallelized because there needs to be some ordering constraints. I have a unit test in check_SCRIPTS which starts the daemon via init.d. The daemon writes out a pid file. There is another unit test script to stop it via init.d. There are various check_PROGRAM binary tests on the daemon when running. The actual tests can be run in any order, but obviously the daemon must be spawned before the rest and, naturally, stopped last. I am not using recursive Automake so it is not possible to simply .NOTPARALLEL the unit tests without affecting the rest of the source tree. This is not practical because the source tree continues to grow in size. For ensuring the stop daemon script at least runs after the start script when make computes the dependency graph, I have a (working) hack. I simply make the stop daemon target shell script depend on the test log of the start script. This works, but it could break in the future with newer Automakes. But in any event, I still don't know what I can do for the binary check_PROGRAMS that test the daemon itself to constrain them to run between the former two? Yours truly, -- Kip Warner | Senior Software Engineer OpenPGP signed/encrypted mail preferred https://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
