Guess it's time to close this one about the subsecond mtimes, and we'll
see what happens next time. (For reference: see also
https://bugs.gnu.org/68325 where we don't try for a millisecond any more ...)
One more follow-up on this. As we saw from the bug reports for the 1.16i
pretest (67894, 67918), the random parallelization failures were back
after this, when autom4te did not support subsecond-mtimes.
As far as I could tell, what was needed was to add
am_cv_sleep_fractional_seconds=false
In order for the Automake testsuite to be able to use sub-second
delays [...]
I installed the patch (plus a tweak to NEWS). (make check and distcheck
ran fine for me, including using the subsecond feature.)
I included all the commentary from your message, Zack, since I thought
it would
Thanks so much, Zack. I will review and apply, most likely tomorrow. -k
In order for the Automake testsuite to be able to use sub-second delays to
control whether certain files are considered newer than others, five(!)
separate pieces of software all need to cooperate: automake itself,
autoconf’s internal “autom4te” utility, the Perl interpreter and its
libraries, the
