Stefano Lattarini [1] solved the problem:
> Anyway, my suggestion is: just start requiring Automake >= 1.12 (or even
> >= 1.13), and use the 'serial-tests' option unconditionally.
>
> Or better again: add the parallel-tests option (supported since automake
> 1.11, and the default since automake 1.13) and convert your testsuite to
> be able to run in parellel mode (that is usually a good idea regardless).
> Then add a custom target (to be run after "make check") that displays the
> content of all the testsuite log files on stdout; e.g.:
>
> display-testsuite-logs:
> for f in $(TEST_LOGS); do printf "\n=== $$f ===\n\n"; cat $$f; done
For procenv, I did the following:
configure.ac:
# automake-1.13 defaults to running tests in parallel. As a consequence,
# it also disables verbose output meaning that procenv output is not
# visible in build logs. Therefore, force old behaviour.
AM_INIT_AUTOMAKE([serial-tests])
Aside - I had though that the following should also work, but it didn't
seem to for me:
Makefile.am:
# Force old behaviour to retain traditional test semantics.
AUTOMAKE_OPTIONS = serial-tests
--
Kind regards,
James.
[1] - https://lists.gnu.org/archive/html/automake/2013-06/msg00051.html
--
James Hunt
____________________________________
#upstart on freenode
http://upstart.ubuntu.com/cookbook
https://lists.ubuntu.com/mailman/listinfo/upstart-devel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
