From: "Frank Ch. Eigler" <fche@elastic.org>
To: dwz@sourceware.org
Subject: patch testsuite - verbose logging
Date: Wed, 6 Jul 2022 13:25:36 -0400 [thread overview]
Message-ID: <YsXFkJRKnjcg0lxP@elastic.org> (raw)
Hi -
The following patch puts "sh -x" tracing data into the dwz.log file.
Accidentally, this makes debuginfod-involving tests pass, since their
stderr DEBUGINFOD_PRGRESS traffic show up in stdout rather than stderr
(which is recorded as a fail).
diff --git a/testsuite/dwz.tests/dwz-tests.exp b/testsuite/dwz.tests/dwz-tests.exp
index 811767f57918..73fe73716302 100644
--- a/testsuite/dwz.tests/dwz-tests.exp
+++ b/testsuite/dwz.tests/dwz-tests.exp
@@ -116,7 +116,8 @@ foreach test $tests {
exec mkdir $dir
cd $dir
- if { [catch { exec sh -e $test } msg] } {
+ if { [catch { exec sh -x -e $test 2>@ stdout } msg] } {
+ verbose -log "$msg"
if { [lindex $::errorCode 0] == "CHILDSTATUS" && \
[lindex $::errorCode 2] == 77 } {
unsupported "$test"
@@ -126,6 +127,7 @@ foreach test $tests {
fail "$test"
}
} else {
+ verbose -log "$msg"
if { [file exists dwz.info ] } {
set info [exec cat dwz.info]
verbose -log "$test:" 1
next reply other threads:[~2022-07-06 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 17:25 Frank Ch. Eigler [this message]
2022-07-12 13:49 ` Mark Wielaard
2022-07-12 14:09 ` Frank Ch. Eigler
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=YsXFkJRKnjcg0lxP@elastic.org \
--to=fche@elastic.org \
--cc=dwz@sourceware.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).