[mojo-edk] Revert port reservation timeout behavior

[mojo-edk] Revert port reservation timeout behavior

This was a bad idea and it makes debugging harder.

Rather than increase the timeout, this reverts the behavior
altogether. We can add an embedder API to explicitly signal
process death in the future.

BUG=612844
R=amistry@chromium.org

Committed: https://crrev.com/2e82ffbd8d4dcf137b893f03edd945fff4a03f9a
Cr-Commit-Position: refs/heads/master@{#396103}

[Anand Mistry (off Chromium), 2016-05-26 00:41:04]

lgtm

[Ken Rockot(use gerrit already), 2016-05-26 00:41:19]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2016-05-26 00:42:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2010783004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2010783004/1

[commit-bot: I haz the power, 2016-05-26 03:37:48]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-26 03:39:23]

Description was changed from

==========
[mojo-edk] Revert port reservation timeout behavior

This was a bad idea and it makes debugging harder.

Rather than increase the timeout, this reverts the behavior
altogether. We can add an embedder API to explicitly signal
process death in the future.

BUG=612844
R=amistry@chromium.org
==========

to

==========
[mojo-edk] Revert port reservation timeout behavior

This was a bad idea and it makes debugging harder.

Rather than increase the timeout, this reverts the behavior
altogether. We can add an embedder API to explicitly signal
process death in the future.

BUG=612844
R=amistry@chromium.org

Committed: https://crrev.com/2e82ffbd8d4dcf137b893f03edd945fff4a03f9a
Cr-Commit-Position: refs/heads/master@{#396103}
==========

[commit-bot: I haz the power, 2016-05-26 03:39:24]

Patchset 1 (id:??) landed as
https://crrev.com/2e82ffbd8d4dcf137b893f03edd945fff4a03f9a
Cr-Commit-Position: refs/heads/master@{#396103}