On Mon, Feb 04, 2013 at 02:31:43PM +0100, Stefano Lattarini wrote: | On 02/04/2013 01:16 AM, Luke Mewburn wrote: | > We use autotest extensively, and our test scenario is rather complex | > and relies upon the existing serial behaviour; | > | I don't follow; if you use autotest, why you also need to rely on the | AUtomake-provided test harnesses? None of the GNU projects using | autotest and that I know of (tar, bison, autoconf, libtool) does so.
My apologies for the brain fade; I conflated "autotest" (from autoconf) with "automake test [harnesses]". We use autotest not automake test. | > If parallel tests supported a dependency graph a la make | > | But it does; in fact, it relies on make to honour such a dependency graph; | quoting from section 15.2.3 "Parallel Test Harness" of the Automake manual | <http://www.gnu.org/software/automake/manual/automake.html#Parallel-Test-Harness>: | [...] | | Or am I missing something else? That makes sense (in light of my confusion of autotest vs automake test.) | > This isn't the only backwards incompatible change made recently, | > and in my humble opinion I think the timeframes introducing | > backwards incompatibility are too aggressive. | > | You are not the only one to think so, and I've come to agree (at least | partially); for some more discussions and background, see: | | <http://lists.gnu.org/archive/html/automake/2013-02/msg00001.html> | <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578> | | So things should proceed more carefully in the future (I hope). Sounds great. regards, Luke.
pgpgW9Oz48OdK.pgp
Description: PGP signature
