> On Nov 20, 2012, at 11:14 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > >> >> "make run_examples" now redirects each example's output to a >> test-suite.log file; can we "tee" it there instead, at least when only >> one example at a time is being run? It's much easier (even from the >> terminal, much less from buildbot's web interface!) to examine example >> output when we've got more than a terse "passed"/"failed" immediately >> available. >> --- >> Roy > This is because we are using the 'parallel-tests' harness, see configure.ac. > This allows tests to be run simultaneously, where stdout is meaningless. > > Granted, it doesn't do much good when we define one test per makefile, > because it doesn't run multiple makefiles in parallel. > > Your solution would be fine for the way we have the tests set up now.
I just refactored the examples to no longer need the FPARSER specific stuff, and also include examples/Make.common where all common rules are defined, helping maintenance. As for the redirection, we can easily enough drop to the serial test harness, or use AM_TESTS_FD_REDIRECT as described here: http://www.gnu.org/software/automake/manual/automake.html#Simple-Tests -Ben ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
