From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/30121] make dejagnu logs more elaborate
Date: Sat, 18 Feb 2023 11:39:11 +0000 [thread overview]
Message-ID: <bug-30121-11298-tyNbfPtQYn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30121-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30121
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Looks helpful. Pushed as:
commit 5ae6047adef9648f50e007b23df09d38de5e0729
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Sat Feb 18 12:36:15 2023 +0100
make dejagnu logs more elaborate
dwz-tests.exp produces totally barebones dwz.log files, basically
duplicating the .sum file. If there are any errors, there's
basically no info to go on.
The patch runs the .sh subtests in -x trace mode, and logs
stdout/stderr to the .log file, so e.g. bunsen can safe-keep it.
Otherwise I believe no-op.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-02-18 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:46 [Bug default/30121] New: " fche at redhat dot com
2023-02-18 11:39 ` mark at klomp dot org [this message]
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=bug-30121-11298-tyNbfPtQYn@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.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).