This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: improving testsuite runtime
- From: Tom Tromey <tromey at redhat dot com>
- To: Ben Elliston <bje at au1 dot ibm dot com>
- Cc: gcc <gcc at gcc dot gnu dot org>
- Date: Thu, 18 Sep 2008 10:44:10 -0600
- Subject: Re: improving testsuite runtime
- References: <1221737823.15255.22.camel@helios>
- Reply-to: tromey at redhat dot com
>>>>> "Ben" == Ben Elliston <bje@au1.ibm.com> writes:
Ben> Using this script and some minor gcc/Makefile.in hacks, I ran the entire
Ben> testsuite in 30% of the current time for a parallel-languages make
Ben> check.
Awesome.
Ben> So, I guess my question is: what now? What do people feel would be
Ben> required to make this usable? I assume that the most pressing thing
Ben> would be to have the build system fold the various .log and .sum files
Ben> together so that they look like they were run as a whole.
Yeah, this seems necessary. Ideally the order ought to be stable, too.
Ben> Another problem is that this is a bit of guesswork. Maybe it would be
Ben> better to drive this from make -j, so that make takes care of the
Ben> scheduling (and we can push the longer tests to the front of the
Ben> dependency list, as we do to improve parallel builds now).
I think 'make -j' is the way to go, since it lets the user easily
control the amount of parallelism.
I often run a single set of tests by passing RUNTESTFLAGS=whatever.exp.
I think this sort of functionality ought to remain available somehow.
Tom