diff options
author | Simon Marchi <simon.marchi@efficios.com> | 2019-08-05 10:21:22 -0400 |
---|---|---|
committer | Simon Marchi <simon.marchi@efficios.com> | 2019-08-05 10:21:48 -0400 |
commit | 580f1034d10934b757703110db068397c0c1e7bb (patch) | |
tree | b8e5fa9c1970e9a6797fd8a048e09fcc963a75fe /gdb/testsuite/gdb.go/package1.go | |
parent | d86bd7cba1965c621b63792179febcf9eeb273ad (diff) | |
download | gdb-580f1034d10934b757703110db068397c0c1e7bb.zip gdb-580f1034d10934b757703110db068397c0c1e7bb.tar.gz gdb-580f1034d10934b757703110db068397c0c1e7bb.tar.bz2 |
Increase timeout in gdb.mi/list-thread-groups-available.exp
Running
make check-read1 TESTS="gdb.mi/list-thread-groups-available.exp"
on my machine results in timeout failures. Running it while having
`tail -F testsuite/gdb.log` on the side shows that the test is never
really blocked, it is just slow at consuming the large output generated
by `-list-thread-groups --available` (which lists all the processes on
the system).
If I increase the timeout to a large value, the test passes in ~30
seconds (compared to under 1 second normally).
Increase the timeout for the particular mi_gdb_test that is long to
execute under read1. The new timeout value is a bit arbitrary. The
default timeout is 10 seconds, so I set the new timeout to be
"old-timeout * 10", so 100 seconds in the typical case.
gdb/testsuite/ChangeLog:
PR gdb/24863
* gdb.mi/list-thread-groups-available.exp: Increase timeout for
-list-thread-groups --available test when running under
check-read1.
Diffstat (limited to 'gdb/testsuite/gdb.go/package1.go')
0 files changed, 0 insertions, 0 deletions