tests: fix a timestamp race in python tests
authorAdam Sampson <ats@offog.org>
Thu, 16 Aug 2012 16:54:41 +0000 (18:54 +0200)
committerStefano Lattarini <stefano.lattarini@gmail.com>
Thu, 16 Aug 2012 16:54:57 +0000 (18:54 +0200)
commit1be71fc819e07c596e4d570844385fcd01f4cef0
tree2520fbcf8bf7b2492130e2d257b934d825b08c0a
parent2bb6c94e04b100143a596ca31e2f1b60590f934e
tests: fix a timestamp race in python tests

Fixes automake bug#12210.

* t/python-missing.sh: Call aclocal and autoconf with the "--force"
option.  We need this because, on fast machines, it's possible for
'mypy.m4' and 'aclocal.m4' to end up with the same timestamp as configure,
so autoconf (without the "--force" options) wouldn't bother to rebuild it,
and would just rerun the previous AM_PATH_PYTHON test, succeeding rather
than failing as expected.
* t/python-am-path-iftrue.sh: Likewise.

Co-authored-by: Stefano Lattarini <stefano.lattarini@gmail.com>
Copyright-paperwork-exempt: yes
Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
t/python-am-path-iftrue.sh
t/python-missing.sh