diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2025-10-15 17:09:13 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-15 17:09:13 -0700 |
| commit | 25c62bca9bc671ae5ce18a79fdef8d6e948c1064 (patch) | |
| tree | 478e1b5a6fc6206f532273d66342bbb64b009418 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp | |
| parent | 6cae29fb3a139c37bbaa09fbaa1179a643a231c9 (diff) | |
| download | llvm-25c62bca9bc671ae5ce18a79fdef8d6e948c1064.zip llvm-25c62bca9bc671ae5ce18a79fdef8d6e948c1064.tar.gz llvm-25c62bca9bc671ae5ce18a79fdef8d6e948c1064.tar.bz2 | |
[lldb-dap] Unify the timeouts for the DAP tests (#163292)
Various DAP tests are specifying their own timeouts, with values ranging
from "1" to "20". Most of them seem arbitrary, but some come with a
comment.
The performance characters of running these tests in CI are
unpredictable (they generally run much slower than developers expect)
and really not something we can make assumptions about. I suspect these
timeouts are a contributing factor to the flakiness of the DAP tests.
This PR unifies the timeouts around a central value in the DAP server.
Fixes #162523
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions