[1/4] testsuite: all: use unique test names for multibyte3 tests

Message ID 20250915154151.2595921-2-rearnsha@arm.com
State New
Headers
Series Cleanup duplicate test names |

Commit Message

Richard Earnshaw Sept. 15, 2025, 3:41 p.m. UTC
  There are two tests of the mutibyte3 source file, with different
options.  As things stand this results in two distinct tests in the
logs with the same name.  Avoid this by adding the optional testname
option to the second test.
---
 gas/testsuite/gas/all/gas.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Patch

diff --git a/gas/testsuite/gas/all/gas.exp b/gas/testsuite/gas/all/gas.exp
index 81f4db24fad..af410834081 100644
--- a/gas/testsuite/gas/all/gas.exp
+++ b/gas/testsuite/gas/all/gas.exp
@@ -578,7 +578,7 @@  run_dump_test "pr27381"
 run_dump_test "multibyte1"
 run_dump_test "multibyte2"
 run_list_test "multibyte3" "--multibyte-handling=warn"
-run_list_test "multibyte3" "-f --multibyte-handling=warn"
+run_list_test "multibyte3" "-f --multibyte-handling=warn" "all multibyte3 -f"
 
 # EVAX has an extra line printed by objdump when there are no relocations,
 # and doesn't appear to enter absolute symbols into the symbol table.