diff options
author | Tom de Vries <tdevries@suse.de> | 2024-09-23 22:03:56 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-09-23 22:03:56 +0200 |
commit | 2edcfde44c5bf915af5fbe2f25ebafd7ba57fad3 (patch) | |
tree | 8627469d2a9ba3da5435a1bbb38b77072dff4702 /gdb/python/py-frame.c | |
parent | 336bb2a1c1d24f5db07394a109f7cd6c5b58b10d (diff) | |
download | binutils-2edcfde44c5bf915af5fbe2f25ebafd7ba57fad3.zip binutils-2edcfde44c5bf915af5fbe2f25ebafd7ba57fad3.tar.gz binutils-2edcfde44c5bf915af5fbe2f25ebafd7ba57fad3.tar.bz2 |
[gdb/testsuite] Avoid large timeout in gdb.base/checkpoint.exp
I ran the testsuite in an environment simulating a stressed system, and the
only test-cases that timed out in gdb.base were gdb.base/checkpoint.exp and
gdb.base/checkpoint-ns.exp (which includes gdb.base/checkpoints.exp).
In test-case gdb.base/checkpoint.exp there's a part where the timeout is
increased with 120 seconds (in the default case that's from 10 to 130), to
accommodate for a single command creating 600+ checkpoints.
Instead, rewrite the test to present a gdb prompt each time a checkpoint is
created, for which the default timeout is sufficient.
Also ensure that the amount of checkpoints added is exactly 600 rather than
600+.
Tested on aarch64-linux.
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/python/py-frame.c')
0 files changed, 0 insertions, 0 deletions