Revert of [Telemetry] Increase timeout after sending SIGTERM

Revert of [Telemetry] Increase timeout after sending SIGTERM (patchset #2 id:20001 of https://codereview.chromium.org/2568033003/ )

Reason for revert:
Testing to see if it caused the issue on Linux on the waterfall: https://bugs.chromium.org/p/chromium/issues/detail?id=674146

Original issue's description:
> [Telemetry] Increase timeout after sending SIGTERM
> 
> To shut down the browser on desktop, we first try to quit the browser normally,
> then send SIGTERM, then wait a while, then send SIGKILL if we still don't see
> that the browser is shut down.
> 
> Apparently, with CHROME_HEADLESS=1, we should be getting a .dmp file on
> SIGTERM, but we see no such file.
> 
> kbr@ suggests that this may simply be because we're not waiting long enough.
> The best result of this CL would be that we start getting useful stack traces
> from these launch failures.
> 
> BUG=catapult:#3074
> 
> Review-Url: https://codereview.chromium.org/2568033003
> Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/e6e0862c81652393de2dd878322e8c0c1e43d428

TBR=kbr@chromium.org,nednguyen@google.com,eakuefner@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=catapult:#3074

Review-Url: https://codereview.chromium.org/2570413002
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/6a5ce5c1dff46439e735135316e21b7355dde479

[eyaich1, 2016-12-14 19:50:21]

The CQ bit was checked by eyaich@chromium.org

[eyaich1, 2016-12-14 19:50:21]

Created Revert of [Telemetry] Increase timeout after sending SIGTERM

[commit-bot: I haz the power, 2016-12-14 19:50:30]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-14 20:19:20]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481745021517090, "parent_rev":
"4c2a679b90126ba81af736f02eeec14683d43e14", "commit_rev":
"6a5ce5c1dff46439e735135316e21b7355dde479"}

[commit-bot: I haz the power, 2016-12-14 20:19:22]

Description was changed from

==========
Revert of [Telemetry] Increase timeout after sending SIGTERM (patchset #2
id:20001 of https://codereview.chromium.org/2568033003/ )

Reason for revert:
Testing to see if it caused the issue on Linux on the waterfall:
https://bugs.chromium.org/p/chromium/issues/detail?id=674146

Original issue's description:
> [Telemetry] Increase timeout after sending SIGTERM
> 
> To shut down the browser on desktop, we first try to quit the browser
normally,
> then send SIGTERM, then wait a while, then send SIGKILL if we still don't see
> that the browser is shut down.
> 
> Apparently, with CHROME_HEADLESS=1, we should be getting a .dmp file on
> SIGTERM, but we see no such file.
> 
> kbr@ suggests that this may simply be because we're not waiting long enough.
> The best result of this CL would be that we start getting useful stack traces
> from these launch failures.
> 
> BUG=catapult:#3074
> 
> Review-Url: https://codereview.chromium.org/2568033003
> Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

TBR=kbr@chromium.org,nednguyen@google.com,eakuefner@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=catapult:#3074
==========

to

==========
Revert of [Telemetry] Increase timeout after sending SIGTERM (patchset #2
id:20001 of https://codereview.chromium.org/2568033003/ )

Reason for revert:
Testing to see if it caused the issue on Linux on the waterfall:
https://bugs.chromium.org/p/chromium/issues/detail?id=674146

Original issue's description:
> [Telemetry] Increase timeout after sending SIGTERM
> 
> To shut down the browser on desktop, we first try to quit the browser
normally,
> then send SIGTERM, then wait a while, then send SIGKILL if we still don't see
> that the browser is shut down.
> 
> Apparently, with CHROME_HEADLESS=1, we should be getting a .dmp file on
> SIGTERM, but we see no such file.
> 
> kbr@ suggests that this may simply be because we're not waiting long enough.
> The best result of this CL would be that we start getting useful stack traces
> from these launch failures.
> 
> BUG=catapult:#3074
> 
> Review-Url: https://codereview.chromium.org/2568033003
> Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

TBR=kbr@chromium.org,nednguyen@google.com,eakuefner@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=catapult:#3074

Review-Url: https://codereview.chromium.org/2570413002
Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-12-14 20:19:23]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...