diff options
| author | 2022-03-10 16:33:08 -0800 | |
|---|---|---|
| committer | 2022-03-10 16:35:08 -0800 | |
| commit | 8523ea02f29935105102fd21e84ea2f8ffdcf5e1 (patch) | |
| tree | a8f0bdcaebd65b60f4744d49fbc137605dcdc3a4 | |
| parent | 2362edf7a6c9c7d756d6e573c4d44837e16fed36 (diff) | |
Bump the timeout on IDumpstateDevice
We're seeing increasingly frequent timeouts due to what appears to be
organic growth in the amount data dumped. These timeouts severely
restrict our ability to triage certain kinds of bugs, so upping the
timeout here.
Bug: 223417101
Test: No timeouts seen locally.
Change-Id: I75aceef2eaa78e5e20f6f27e76b62131f781a14f
| -rw-r--r-- | cmds/dumpstate/dumpstate.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cmds/dumpstate/dumpstate.cpp b/cmds/dumpstate/dumpstate.cpp index 0e9ce897bc..24b201f8ab 100644 --- a/cmds/dumpstate/dumpstate.cpp +++ b/cmds/dumpstate/dumpstate.cpp @@ -2418,7 +2418,7 @@ void Dumpstate::DumpstateBoard(int out_fd) { // Given that bugreport is required to diagnose failures, it's better to set an arbitrary amount // of timeout for IDumpstateDevice than to block the rest of bugreport. In the timeout case, we // will kill the HAL and grab whatever it dumped in time. - constexpr size_t timeout_sec = 30; + constexpr size_t timeout_sec = 45; if (dumpstate_hal_handle_aidl != nullptr) { DoDumpstateBoardAidl(dumpstate_hal_handle_aidl, dumpstate_fds, options_->bugreport_mode, |