[binutils-gdb] gdb/testsuite: Remove duplicates from gdb.mi/mi-nonstop.exp

[binutils-gdb] gdb/testsuite: Remove duplicates from gdb.mi/mi-nonstop.exp

[Lancelot SIX]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=94e3acde23ca8e68e14817661740e692d3f3e738

commit 94e3acde23ca8e68e14817661740e692d3f3e738
Author: Lancelot SIX <lsix@lancelotsix.com>
Date:   Tue Nov 23 13:35:47 2021 +0000

    gdb/testsuite: Remove duplicates from gdb.mi/mi-nonstop.exp
    
    When running the testsuite, I have:
    
        Running .../gdb/testsuite/gdb.mi/mi-nonstop.exp ...
        DUPLICATE: gdb.mi/mi-nonstop.exp: check varobj, w1, 1
        DUPLICATE: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread
    
    Fix by adjusting the problematic test names.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.mi/mi-nonstop.exp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.mi/mi-nonstop.exp b/gdb/testsuite/gdb.mi/mi-nonstop.exp
index 0ed6c2ef5f6..fe9392e314e 100644
--- a/gdb/testsuite/gdb.mi/mi-nonstop.exp
+++ b/gdb/testsuite/gdb.mi/mi-nonstop.exp
@@ -112,7 +112,7 @@ mi_check_thread_states {"running" "running" "stopped"} "thread state, stop on co
 # Check that when we update all varobj, we don't get no error about varobj
 # bound to running thread.
 mi_varobj_update * {I_W1} "update varobj, 2"
-mi_check_varobj_value I_W1 3 "check varobj, w1, 1"
+mi_check_varobj_value I_W1 3 "check varobj, w1, 2"
 
 
 # Check that stack commands are allowed on a stopped thread, even if some other threads
@@ -147,6 +147,6 @@ if { [mi_is_target_remote] } {
 # See that we can still poke other threads.
 mi_gdb_test "-stack-list-frames --thread 3" \
     "\\^done,stack=\\\[frame={level=\"0\",addr=\".*\",func=\"break_at_me\".*" \
-    "stacktrace of stopped thread"
+    "stacktrace of stopped thread, 2"
 
 mi_gdb_exit