This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Distributing 'make check' across a cluster

From: Diego Novillo <dnovillo at google dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: Diego Novillo <diego dot novillo at gmail dot com>, Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org, gcc <gcc at gcc dot gnu dot org>
Date: Mon, 04 Jun 2012 21:47:48 -0400
Subject: Re: Distributing 'make check' across a cluster
References: <4FC7791E.6040407@gmail.com> <Pine.LNX.4.64.1205311420120.7338@digraph.polyomino.org.uk>

On 12-05-31 10:28 , Joseph S. Myers wrote:

That is however installed testing with a complete source tree available
(but not a build tree); I don't know exactly what is needed from outside
the testsuite/ directory (but see
libstdc++-v3/testsuite/lib/libstdc++.exp:libstdc++_init for what happens
during the testsuite setup).

Thanks.

C, C++, Fortran, Obj-C and Obj-C++ testing have been known to work in the
past for installed testing.  Java, Ada and Go are quite likely to have
problems; I don't think I've tried installed testing for libmudflap,
libffi, libitm, libatomic (but it should work for libgomp).

Both libmudflap and libgomp are currently giving me grief because they need mfconfig.exp and gompconfig.exp. Both of which are generated at build-time, so I don't have them around.

They mostly set GCC_UNDER_TEST and a couple other things, so I'll just generate them in my scripts.

Diego.

Follow-Ups:
- Re: Distributing 'make check' across a cluster
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]