gdb/testsuite: resolve duplicate test name in gdb.trace/signal.exp
authorAndrew Burgess <aburgess@redhat.com>
Tue, 31 May 2022 08:21:20 +0000 (09:21 +0100)
committerAndrew Burgess <aburgess@redhat.com>
Tue, 31 May 2022 08:23:32 +0000 (09:23 +0100)
Spotted a duplicate test name in gdb.trace/signal.exp, resolved in
this commit by making use of 'with_test_prefix'.

gdb/testsuite/gdb.trace/signal.exp

index 782abeb69d388f533903003604ad9de238895d58..da9f0603a5b91157e643c9399538caf801568c89 100644 (file)
@@ -125,7 +125,9 @@ delete_breakpoints
 gdb_breakpoint "start" qualified
 gdb_continue_to_breakpoint "continue to start"
 
-gdb_assert { 0 == [get_integer_valueof "counter" "1"] } "counter is zero"
+with_test_prefix "counter is zero" {
+    gdb_assert { 0 == [get_integer_valueof "counter" "1"] } "assert check"
+}
 
 delete_breakpoints
 
@@ -147,8 +149,10 @@ gdb_test_no_output "tstop"
 
 set iterations [get_integer_valueof "iterations" "0"]
 
-gdb_assert { $iterations == [get_integer_valueof "counter" "0"] } \
-    "iterations equals to counter"
+with_test_prefix "iterations equals to counter" {
+    gdb_assert { $iterations == [get_integer_valueof "counter" "0"] } \
+       "assert check"
+}
 
 # Record the hit times of each tracepoint in this array.
 array set tracepoint_hits { }