On 12-06-11 10:24 , Joseph S. Myers wrote:
I don't see any reference to gompconfig.exp anywhere in the source tree.
(But generally the Tcl code initializing a testsuite should do setup of
anything outside site.exp, like in the libstdc++ testsuite.)
Yeah, sorry. gompconfig.exp is a local patch
On Mon, 4 Jun 2012, Diego Novillo wrote:
> > 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 (
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
d
On 05/31/2012 05:22 PM, Benjamin Kosnik wrote:
Thanks. Having the source tree available is not a problem, as I
require it to copy the actual testsuites into the work tree. Adding
a few more files from the source tree would not be a problem.
From:
http://gcc.gnu.org/onlinedocs/libstdc++/manu
> Thanks. Having the source tree available is not a problem, as I
> require it to copy the actual testsuites into the work tree. Adding
> a few more files from the source tree would not be a problem.
From:
http://gcc.gnu.org/onlinedocs/libstdc++/manual/test.html
You can run the tests with a co
On 12-05-31 10:28 , Joseph S. Myers wrote:
libstdc++ definitely works with installed testing (there may be a bug or
two, e.g. PR 23867, that mean a few tests don't get run that way); it's
how Mentor's testing works.
Great.
That is however installed testing with a complete source tree availab
On Thu, 31 May 2012, Diego Novillo wrote:
> This is working pretty well for everything outside of libstdc++. I can reduce
> testing from about an hour to a few minutes (we test -m32 and -m64).
>
> libstdc++ seems to be doing a few other manipulations of site.exp and
> additional setup that's def
Ben, we briefly chatted about this earlier. Here's more details.
I'm trying to distribute GCC testing across nodes in a cluster that do
not share a common file system. The strategy is (roughly) to avoid
using the build tree and distribute:
1- The installed tree out of 'make install'.
2- A
