From: Jonathan Wakely Date: Fri, 10 Apr 2015 19:59:32 +0000 (+0100) Subject: test.xml: Improve documentation on running a subset of tests. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=cd80c79ce739ddcd7fb50b731c02ddd1e51479aa;p=gcc.git test.xml: Improve documentation on running a subset of tests. * doc/xml/manual/test.xml: Improve documentation on running a subset of tests. * doc/html/manual/test.html: Regenerate. From-SVN: r221985 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 6aa11f62981..e66a7978c98 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2015-04-10 Jonathan Wakely + + * doc/xml/manual/test.xml: Improve documentation on running a subset + of tests. + * doc/html/manual/test.html: Regenerate. + 2015-04-10 Bill Schmidt * config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update diff --git a/libstdc++-v3/doc/html/manual/test.html b/libstdc++-v3/doc/html/manual/test.html index 78ffb226994..893cf7242e3 100644 --- a/libstdc++-v3/doc/html/manual/test.html +++ b/libstdc++-v3/doc/html/manual/test.html @@ -166,12 +166,20 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="-v"

 make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v"
 

- To run a subset of the library tests, you will need to generate - the testsuite_files file by running + To run a subset of the library tests, you can either generate the + testsuite_files file (described below) by running make testsuite_files in the - libbuilddir/testsuite directory, described - below. Edit the file to remove the tests you don't want and - then run the testsuite as normal. + libbuilddir/testsuite directory, then edit the + file to remove the tests you don't want and then run the testsuite as + normal, or you can specify a testsuite and a subset of tests in the + RUNTESTFLAGS variable. +

+ For example, to run only the tests for containers you could use: +

+make check-target-libstdc++-v3 RUNTESTFLAGS="conformance.exp=23_containers/*"
+

+ When combining this with other options in RUNTESTFLAGS the + testsuite.exp=testfiles options must come first.

There are two ways to run on a simulator: set up DEJAGNU to point to a specially crafted site.exp, or pass down --target_board flags. diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml index d3d22647193..456c48b2639 100644 --- a/libstdc++-v3/doc/xml/manual/test.xml +++ b/libstdc++-v3/doc/xml/manual/test.xml @@ -279,12 +279,26 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v" - To run a subset of the library tests, you will need to generate - the testsuite_files file by running + To run a subset of the library tests, you can either generate the + testsuite_files file (described below) by running make testsuite_files in the - libbuilddir/testsuite directory, described - below. Edit the file to remove the tests you don't want and - then run the testsuite as normal. + libbuilddir/testsuite directory, then edit the + file to remove the tests you don't want and then run the testsuite as + normal, or you can specify a testsuite and a subset of tests in the + RUNTESTFLAGS variable. + + + + For example, to run only the tests for containers you could use: + + + +make check-target-libstdc++-v3 RUNTESTFLAGS="conformance.exp=23_containers/*" + + + + When combining this with other options in RUNTESTFLAGS the + testsuite.exp=testfiles options must come first.