From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Add log line to testsuite output
Date: Sat, 16 Sep 2023 00:04:27 +0100 [thread overview]
Message-ID: <20230915230539.2328463-1-jwakely@redhat.com> (raw)
Tested aarch64-linux. Pushed to trunk.
This makes it easier to debug the problem when a test isn't running
because there's a testsuite_files that doesn't include it.
-- >8 --
Write a line to the log when using a testsuite_files file.
libstdc++-v3/ChangeLog:
* testsuite/libstdc++-dg/conformance.exp: Add log line when
using testsuite_files.
---
libstdc++-v3/testsuite/libstdc++-dg/conformance.exp | 1 +
1 file changed, 1 insertion(+)
diff --git a/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp b/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
index 76679739823..96dcc1f8cff 100644
--- a/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
+++ b/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
@@ -44,6 +44,7 @@ if {[info exists blddir]} {
}
if {[info exists tests_file] && [file exists $tests_file]} {
set f [open $tests_file]
+ verbose -log "reading test files from $tests_file" 1
while { ! [eof $f] } {
set t [gets $f]
if { [string length "$t"] != 0 } {
--
2.41.0
reply other threads:[~2023-09-15 23:05 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=20230915230539.2328463-1-jwakely@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).