From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCHv2 0/2] Cleanup testsuite temporary files
Date: Tue, 4 Oct 2022 15:20:12 +0100 [thread overview]
Message-ID: <cover.1664893145.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1664721741.git.aburgess@redhat.com>
I spotted that we have a couple of temporary files being written to
the build/gdb/testsuite/ directory, not to the per test script output
directory.
The following two patches fix the issues I spotted.
Changes since v1:
- Patch #1 updated inline with Lancelot's suggestion,
- Patch #2 updated inline with Pedro's suggestion.
---
Andrew Burgess (2):
gdb/testsuite: avoid creating files in gdb/testsuite directory
gdb/testsuite: avoid temporary file in gdb/testsuite (unittest.exp)
.../gdb.dwarf2/dw2-using-debug-str.exp | 2 +-
gdb/testsuite/gdb.gdb/unittest.exp | 46 +++++---
gdb/testsuite/lib/gdb.exp | 110 ++++++++++++++++++
3 files changed, 138 insertions(+), 20 deletions(-)
--
2.25.4
next prev parent reply other threads:[~2022-10-04 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 14:43 [PATCH " Andrew Burgess
2022-10-02 14:43 ` [PATCH 1/2] gdb/testsuite: avoid creating files in gdb/testsuite directory Andrew Burgess
2022-10-03 11:12 ` Lancelot SIX
2022-10-03 16:06 ` Andrew Burgess
2022-10-03 18:51 ` Pedro Alves
2022-10-04 8:55 ` Andrew Burgess
2022-10-04 9:08 ` Andrew Burgess
2022-10-04 12:15 ` Pedro Alves
2022-10-02 14:43 ` [PATCH 2/2] gdb/testsuite: avoid temporary file in gdb/testsuite Andrew Burgess
2022-10-04 14:20 ` Andrew Burgess [this message]
2022-10-04 14:20 ` [PATCHv2 1/2] gdb/testsuite: avoid creating files in gdb/testsuite directory Andrew Burgess
2022-10-04 14:20 ` [PATCHv2 2/2] gdb/testsuite: avoid temporary file in gdb/testsuite (unittest.exp) Andrew Burgess
2022-10-14 16:28 ` [PATCHv2 0/2] Cleanup testsuite temporary files Tom Tromey
2022-10-19 11:20 ` Andrew Burgess
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=cover.1664893145.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@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).