From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [patch] Improve docs on running libstdc++ tests
Date: Fri, 10 Apr 2015 20:00:00 -0000 [thread overview]
Message-ID: <20150410200051.GZ9755@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 117 bytes --]
This came up on IRC today. Editing testsuite_files isn't the only way
to run a subset of tests.
Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1772 bytes --]
commit 97f1afff492953efa83e07fdbf66af2b77a5ee89
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Apr 10 20:58:54 2015 +0100
* doc/xml/manual/test.xml: Improve documentation on running a subset
of tests.
* doc/html/manual/test.html: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml
index d3d2264..456c48b 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"
</programlisting>
<para>
- To run a subset of the library tests, you will need to generate
- the <emphasis>testsuite_files</emphasis> file by running
+ To run a subset of the library tests, you can either generate the
+ <emphasis>testsuite_files</emphasis> file (described below) by running
<command>make testsuite_files</command> in the
- <emphasis>libbuilddir/testsuite</emphasis> directory, described
- below. Edit the file to remove the tests you don't want and
- then run the testsuite as normal.
+ <emphasis>libbuilddir/testsuite</emphasis> 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.
+ </para>
+
+ <para>
+ For example, to run only the tests for containers you could use:
+ </para>
+
+<programlisting>
+make check-target-libstdc++-v3 RUNTESTFLAGS="conformance.exp=23_containers/*"
+</programlisting>
+
+ <para>
+ When combining this with other options in RUNTESTFLAGS the
+ <emphasis>testsuite.exp=testfiles</emphasis> options must come first.
</para>
<para>
reply other threads:[~2015-04-10 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150410200051.GZ9755@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).