From: Markus Metzger via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/4] testsuite, gdb.python: make py-record-*.exp test names unique
Date: Thu, 17 Dec 2020 16:12:10 +0100 [thread overview]
Message-ID: <20201217151212.1179058-3-markus.t.metzger@intel.com> (raw)
In-Reply-To: <20201217151212.1179058-1-markus.t.metzger@intel.com>
gdb/testsuite/ChangeLog:
2020-12-14 Markus Metzger <markus.t.metzger@intel.com>
* gdb.python/py-record-btrace.exp: Make test names unique.
* gdb.python/py-record-full.exp: Likewise.
---
gdb/testsuite/gdb.python/py-record-btrace.exp | 7 +++++--
gdb/testsuite/gdb.python/py-record-full.exp | 7 +++++--
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/gdb/testsuite/gdb.python/py-record-btrace.exp b/gdb/testsuite/gdb.python/py-record-btrace.exp
index 3a84cbe7ac4..d113ed640fd 100644
--- a/gdb/testsuite/gdb.python/py-record-btrace.exp
+++ b/gdb/testsuite/gdb.python/py-record-btrace.exp
@@ -44,10 +44,13 @@ with_test_prefix "no or double record" {
gdb_test "python print(gdb.current_recording())" "None"
gdb_test_no_output "python gdb.start_recording(\"btrace\")"
- gdb_test "python gdb.start_recording(\"btrace\")" ".*gdb\.error: The process is already being recorded\..*"
+ gdb_test "python gdb.start_recording(\"btrace\")" \
+ ".*gdb\.error: The process is already being recorded\..*" \
+ "already recording"
gdb_test_no_output "python gdb.stop_recording()" "first"
- gdb_test "python gdb.stop_recording()" ".*gdb\.error: No recording is currently active\..*" "second"
+ gdb_test "python gdb.stop_recording()" \
+ ".*gdb\.error: No recording is currently active\..*" "second"
}
with_test_prefix "preopened record btrace" {
diff --git a/gdb/testsuite/gdb.python/py-record-full.exp b/gdb/testsuite/gdb.python/py-record-full.exp
index a1f24a3634f..0b67788d4fd 100644
--- a/gdb/testsuite/gdb.python/py-record-full.exp
+++ b/gdb/testsuite/gdb.python/py-record-full.exp
@@ -44,10 +44,13 @@ with_test_prefix "no or double record" {
gdb_test "python print(gdb.current_recording())" "None"
gdb_test_no_output "python gdb.start_recording(\"full\")"
- gdb_test "python gdb.start_recording(\"full\")" ".*gdb\.error: The process is already being recorded\..*"
+ gdb_test "python gdb.start_recording(\"full\")" \
+ ".*gdb\.error: The process is already being recorded\..*" \
+ "already recording"
gdb_test_no_output "python gdb.stop_recording()" "first"
- gdb_test "python gdb.stop_recording()" ".*gdb\.error: No recording is currently active\..*" "second"
+ gdb_test "python gdb.stop_recording()" \
+ ".*gdb\.error: No recording is currently active\..*" "second"
}
with_test_prefix "preopened record full" {
--
2.26.2
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2020-12-17 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:12 [PATCH] gdb, record: rephrase the 'not recording' error message Markus Metzger via Gdb-patches
2020-12-17 15:12 ` [PATCH 1/4] testsuite, gdb.btrace: make test names unique Markus Metzger via Gdb-patches
2020-12-18 19:34 ` Simon Marchi via Gdb-patches
2020-12-21 7:26 ` Metzger, Markus T via Gdb-patches
2020-12-17 15:12 ` Markus Metzger via Gdb-patches [this message]
2020-12-18 19:35 ` [PATCH 2/4] testsuite, gdb.python: make py-record-*.exp " Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 3/4] testsuite, gdb.btrace: skip multi-inferior.exp on gdbserver targets Markus Metzger via Gdb-patches
2020-12-18 19:49 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches
2020-12-21 13:50 ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 4/4] testsuite, gdb.btrace: fix 32-bit PIE false positives Markus Metzger via Gdb-patches
2020-12-18 20:01 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches
2020-12-18 19:18 ` [PATCH] gdb, record: rephrase the 'not recording' error message Simon Marchi via Gdb-patches
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=20201217151212.1179058-3-markus.t.metzger@intel.com \
--to=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/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