diff options
| author | Simon Marchi <simon.marchi@polymtl.ca> | 2022-09-23 09:45:24 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2022-09-26 17:28:21 -0400 |
| commit | 687e348e720a1fcd3850324c9f0ce20b97b456b5 (patch) | |
| tree | d8b8ccd471843751605ed2c95b25994c32cb5ea2 /binutils/objcopy.c | |
| parent | fe441584bb9524e07dea468079d6abce859ad03c (diff) | |
| download | binutils-687e348e720a1fcd3850324c9f0ce20b97b456b5.zip binutils-687e348e720a1fcd3850324c9f0ce20b97b456b5.tar.gz binutils-687e348e720a1fcd3850324c9f0ce20b97b456b5.tar.bz2 | |
gdb/testsuite: bump duration for the whole test in do_self_tests
When running gdb.gdb/python-helper.exp, I get some timeouts:
continue
Continuing.
print 1
FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb (timeout)
At this time, GDB is actually processing the stop and reading in some
CUs. selftest_setup does bump the timeout, but it's not for the whole
test.
Since debugging GDB with GDB is (unfortunately) a bit slow, bump the
timeout for the whole duration of the setup and body. On my optimized
build, the command takes just a bit more than the current timeout of 10
seconds. But it's much slower if running the test on an unoptimized
build, so I think it's necessary to bump the timeout for that in any
case.
Change-Id: I4d38285870e76c94f9d0bfdb60648a2e7f2cfa5d
Diffstat (limited to 'binutils/objcopy.c')
0 files changed, 0 insertions, 0 deletions