diff options
author | Tom de Vries <tdevries@suse.de> | 2021-10-06 01:27:58 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-10-06 01:27:58 +0200 |
commit | 1457d766df2c6925e4af7a013c92ce7495cb0d87 (patch) | |
tree | dcc8ad30971776d1b50800f25fc3b4ac5d64fba1 /bfd | |
parent | 58d82c2c59814c6d3f56a4134a777ae6ec292460 (diff) | |
download | gdb-1457d766df2c6925e4af7a013c92ce7495cb0d87.zip gdb-1457d766df2c6925e4af7a013c92ce7495cb0d87.tar.gz gdb-1457d766df2c6925e4af7a013c92ce7495cb0d87.tar.bz2 |
[gdb/testsuite] Make tui testing less verbose
Currently, tui testing is rather verbose. When using these RUNTESTFLAGS to
pick up all tui tests (17 in total):
...
rtf=$(echo $(cd src/gdb/testsuite/; find gdb.* -type f -name *.exp* \
| xargs grep -l tuiterm_env) )
...
we have:
...
$ wc -l gdb.log
120592 gdb.log
...
Most of the output is related to controlling the tui screen, but that does
not give a top-level sense of how the test-case progresses.
Put differently: a lot of bandwith is used to describe how we arrive at a
certain tui screen state. But we don't actually always show the state we
arrive at, unless there's a FAIL.
And if there's say, a PASS that should actually be FAILing, it's hard to
detect.
Fix this by:
- dropping the -log on the call to verbose in _log. We still can get the
same info back using runtest -v.
- dumping the screen or box that we're checking, also when the test passes.
Brings down verbosity to something more reasonable:
...
$ wc -l gdb.log
3221 gdb.log
...
Tested on x86_64-linux.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions