From 9d13bd76f84db860e0541dbdddf54e650019fbad Mon Sep 17 00:00:00 2001 From: Bernd Edlinger Date: Fri, 9 Aug 2024 10:39:56 +0200 Subject: Fix test failure when TUI is not enabled This adds a missing allow_tui_tests guard. When tui is not enabled this test case does typically fail: FAIL: gdb.base/new-ui.exp: do_test_invalid_args: new-ui with tui Approved-By: Tom de Vries --- gdb/testsuite/gdb.base/new-ui.exp | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'gdb') diff --git a/gdb/testsuite/gdb.base/new-ui.exp b/gdb/testsuite/gdb.base/new-ui.exp index 2dfcbf7..a56d213 100644 --- a/gdb/testsuite/gdb.base/new-ui.exp +++ b/gdb/testsuite/gdb.base/new-ui.exp @@ -184,9 +184,11 @@ proc_with_prefix do_test_invalid_args {} { "new-ui with bad interpreter name" # Test that the TUI cannot be used for a new UI. - gdb_test "new-ui tui $extra_tty_name" \ - "interpreter 'tui' cannot be used with a new UI" \ - "new-ui with tui" + if [allow_tui_tests] { + gdb_test "new-ui tui $extra_tty_name" \ + "interpreter 'tui' cannot be used with a new UI" \ + "new-ui with tui" + } # Test that we can continue working normally. if ![runto_main] { -- cgit v1.1