diff options
author | Tom de Vries <tdevries@suse.de> | 2023-11-24 15:38:17 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2023-11-24 15:38:17 +0100 |
commit | 15717656549b6af941511dde20a51475c932645e (patch) | |
tree | bcb1e444616105ad4118c7cd4c35c700e3d242d9 /.gitattributes | |
parent | fa1c74b22aa8c465974ddf792395d8e313199a52 (diff) | |
download | gdb-15717656549b6af941511dde20a51475c932645e.zip gdb-15717656549b6af941511dde20a51475c932645e.tar.gz gdb-15717656549b6af941511dde20a51475c932645e.tar.bz2 |
[gdb/testsuite] Two fixes in gdb.python/tui-window-disabled.exp
I ran test-case gdb.python/tui-window-disabled.exp on a configuration without
python support, and ran into:
...
PASS: $exp: cleanup_properly=True: initial restart: set pagination off
UNSUPPORTED: $exp: cleanup_properly=True: couldn't restart GDB
PASS: $exp: cleanup_properly=False: initial restart: set pagination off
UNSUPPORTED: $exp: cleanup_properly=False: couldn't restart GDB
...
After looking into the test-case, I realized that this is a consequence of
!allow_python_tests.
Handle this instead by requiring allow_python_tests, such that we get the usual
and more clear:
...
UNSUPPORTED: $exp: require failed: allow_python_tests
...
Also fix a return without value in clean_restart_and_setup, which if triggered
would cause:
...
ERROR: expected boolean value but got ""
...
Tested on x86_64-linux.
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions