From 10e38c94322124d5b9c1528a6c86a0559ce75269 Mon Sep 17 00:00:00 2001 From: Kweku Adams Date: Thu, 13 Sep 2018 15:48:27 -0700 Subject: Increasing TombstoneSection timeout to 2 minutes. Java trace dumps can take significantly longer than 30 seconds. Testing suggests that 2 minutes should be ample time. Bug: 111729299 Test: 'adb shell incident' and ensure the section doesn't time out. Change-Id: I35e09fc1ca608122a1a352985ea3741f6ea0a344 (cherry picked from commit 0f7167947a6e3180da0964ec6187f9f01642fb6d) --- cmds/incidentd/src/Section.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmds/incidentd/src/Section.h b/cmds/incidentd/src/Section.h index a031a15fe7c9..2f89370b0d26 100644 --- a/cmds/incidentd/src/Section.h +++ b/cmds/incidentd/src/Section.h @@ -173,7 +173,7 @@ private: */ class TombstoneSection : public WorkerThreadSection { public: - TombstoneSection(int id, const char* type, int64_t timeoutMs = 30000 /* 30 seconds */); + TombstoneSection(int id, const char* type, int64_t timeoutMs = 120000 /* 2 minutes */); virtual ~TombstoneSection(); virtual status_t BlockingCall(int pipeWriteFd) const; -- cgit v1.2.3-59-g8ed1b