Revert of GPU Watchdog to check I/O before terminating GPU process

Revert of GPU Watchdog to check I/O before terminating GPU process (patchset #5 id:120001 of https://codereview.chromium.org/1980263002/ )

Reason for revert:
This CL seems to have caused intermittent assertion failures in the context_lost_tests on the commit queue and reliable assertion failures on some of the GPU bots. See http://crbug.com/619196 .

Original issue's description:
> GPU Watchdog to check I/O before terminating
>
> The idea is to try to do an unbuffered write in GPU watchdog
> just before crashing the process. If the process is slow due
> to heavy I/O this should give it more time to unblock.
>
> This should theoretically help with some of GPU hangs.
>
> BUG=612607
>
> Committed: https://crrev.com/4015b488f743a7399e3362fd49917f494ff7caaf
> Cr-Commit-Position: refs/heads/master@{#399222}

TBR=jbauman@chromium.org,wfh@chromium.org,nick@chromium.org,manzagop@chromium.org,pmonette@chromium.org,brucedawson@chromium.org,stanisc@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612607
Committed: https://crrev.com/40684e97fcc0cc24a2504f0dc2679a3b88557d9b
Cr-Commit-Position: refs/heads/master@{#399998}

[Ken Russell (switch to Gerrit), 2016-06-15 18:34:01]

The CQ bit was checked by kbr@chromium.org

[Ken Russell (switch to Gerrit), 2016-06-15 18:34:02]

Created Revert of GPU Watchdog to check I/O before terminating GPU process

[commit-bot: I haz the power, 2016-06-15 18:34:41]

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

[Will Harris, 2016-06-15 19:29:04]

were you able to gather any data from canary before the revert?

[commit-bot: I haz the power, 2016-06-15 20:18:41]

Description was changed from

==========
Revert of GPU Watchdog to check I/O before terminating GPU process (patchset #5
id:120001 of https://codereview.chromium.org/1980263002/ )

Reason for revert:
This CL seems to have caused intermittent assertion failures in the
context_lost_tests on the commit queue and reliable assertion failures on some
of the GPU bots. See http://crbug.com/619196 .


Original issue's description:
> GPU Watchdog to check I/O before terminating
> 
> The idea is to try to do an unbuffered write in GPU watchdog
> just before crashing the process. If the process is slow due
> to heavy I/O this should give it more time to unblock.
> 
> This should theoretically help with some of GPU hangs.
> 
> BUG=612607
> 
> Committed: https://crrev.com/4015b488f743a7399e3362fd49917f494ff7caaf
> Cr-Commit-Position: refs/heads/master@{#399222}

TBR=jbauman@chromium.org,wfh@chromium.org,nick@chromium.org,manzagop@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612607
==========

to

==========
Revert of GPU Watchdog to check I/O before terminating GPU process (patchset #5
id:120001 of https://codereview.chromium.org/1980263002/ )

Reason for revert:
This CL seems to have caused intermittent assertion failures in the
context_lost_tests on the commit queue and reliable assertion failures on some
of the GPU bots. See http://crbug.com/619196 .


Original issue's description:
> GPU Watchdog to check I/O before terminating
> 
> The idea is to try to do an unbuffered write in GPU watchdog
> just before crashing the process. If the process is slow due
> to heavy I/O this should give it more time to unblock.
> 
> This should theoretically help with some of GPU hangs.
> 
> BUG=612607
> 
> Committed: https://crrev.com/4015b488f743a7399e3362fd49917f494ff7caaf
> Cr-Commit-Position: refs/heads/master@{#399222}

TBR=jbauman@chromium.org,wfh@chromium.org,nick@chromium.org,manzagop@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612607
==========

[commit-bot: I haz the power, 2016-06-15 20:18:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-15 20:21:04]

Description was changed from

==========
Revert of GPU Watchdog to check I/O before terminating GPU process (patchset #5
id:120001 of https://codereview.chromium.org/1980263002/ )

Reason for revert:
This CL seems to have caused intermittent assertion failures in the
context_lost_tests on the commit queue and reliable assertion failures on some
of the GPU bots. See http://crbug.com/619196 .


Original issue's description:
> GPU Watchdog to check I/O before terminating
> 
> The idea is to try to do an unbuffered write in GPU watchdog
> just before crashing the process. If the process is slow due
> to heavy I/O this should give it more time to unblock.
> 
> This should theoretically help with some of GPU hangs.
> 
> BUG=612607
> 
> Committed: https://crrev.com/4015b488f743a7399e3362fd49917f494ff7caaf
> Cr-Commit-Position: refs/heads/master@{#399222}

TBR=jbauman@chromium.org,wfh@chromium.org,nick@chromium.org,manzagop@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612607
==========

to

==========
Revert of GPU Watchdog to check I/O before terminating GPU process (patchset #5
id:120001 of https://codereview.chromium.org/1980263002/ )

Reason for revert:
This CL seems to have caused intermittent assertion failures in the
context_lost_tests on the commit queue and reliable assertion failures on some
of the GPU bots. See http://crbug.com/619196 .

Original issue's description:
> GPU Watchdog to check I/O before terminating
>
> The idea is to try to do an unbuffered write in GPU watchdog
> just before crashing the process. If the process is slow due
> to heavy I/O this should give it more time to unblock.
>
> This should theoretically help with some of GPU hangs.
>
> BUG=612607
>
> Committed: https://crrev.com/4015b488f743a7399e3362fd49917f494ff7caaf
> Cr-Commit-Position: refs/heads/master@{#399222}

TBR=jbauman@chromium.org,wfh@chromium.org,nick@chromium.org,manzagop@chromium...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612607

Committed: https://crrev.com/40684e97fcc0cc24a2504f0dc2679a3b88557d9b
Cr-Commit-Position: refs/heads/master@{#399998}
==========

[commit-bot: I haz the power, 2016-06-15 20:21:05]

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

[brucedawson, 2016-06-16 00:26:10]

On 2016/06/15 19:29:04, Will Harris wrote:
> were you able to gather any data from canary before the revert?

Yes. In at least some cases there were long I/O delays in the hangs. stanisc@
has the details and can share on the bug or elsewhere.

[stanisc, 2016-06-16 00:46:09]

On 2016/06/16 00:26:10, brucedawson wrote:
> On 2016/06/15 19:29:04, Will Harris wrote:
> > were you able to gather any data from canary before the revert?
> 
> Yes. In at least some cases there were long I/O delays in the hangs. stanisc@
> has the details and can share on the bug or elsewhere.

I'll update issue 612607.