Disabling NOTREACHED which we're hitting flakily in browser tests.

Disabling NOTREACHED which we're hitting flakily in browser tests.

I have no idea how bad it is that we're hitting this limit; I'm just
doing this to stop the tests from flaking.

BUG=webrtc:6484
Committed: https://crrev.com/6eaa55867b449df992752c1df540ec42f9d9b057
Cr-Commit-Position: refs/heads/master@{#14974}

[phoglund, 2016-11-03 10:59:38]

phoglund@webrtc.org changed reviewers:
+ asapersson@webrtc.org

[phoglund, 2016-11-03 11:00:41]

phoglund@webrtc.org changed reviewers:
+ stefan@webrtc.org

[åsapersson, 2016-11-03 12:17:53]

lgtm

[phoglund, 2016-11-03 12:57:20]

The CQ bit was checked by phoglund@webrtc.org

[commit-bot: I haz the power, 2016-11-03 12:57:30]

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

[commit-bot: I haz the power, 2016-11-03 13:00:19]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-03 13:00:20]

Try jobs failed on following builders:
  presubmit on master.tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/presubmit/builds/9788)

[phoglund, 2016-11-03 13:29:33]

Stefan, owner stamp please?

[stefan-webrtc, 2016-11-08 08:54:55]

lgtm, although hopefully this has already been fixed.

[phoglund, 2016-11-08 09:17:36]

It has not, so I'm landing this now.

[phoglund, 2016-11-08 09:18:21]

On 2016/11/08 09:17:36, phoglund wrote:
> It has not, so I'm landing this now.

Recent example, which happened after the libvpx roll:
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Win10%20Tester/buil...

[phoglund, 2016-11-08 09:18:25]

The CQ bit was checked by phoglund@webrtc.org

[commit-bot: I haz the power, 2016-11-08 09:18:29]

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

[phoglund, 2016-11-08 09:20:45]

The CQ bit was unchecked by phoglund@webrtc.org

[phoglund, 2016-11-08 09:21:09]

On 2016/11/08 09:18:29, commit-bot: I haz the power wrote:
> CQ is trying da patch. Follow status at
>  
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

Or wait actually, that build was from yesterday. Let me investigate a bit
more...

[phoglund, 2016-11-08 13:30:14]

On 2016/11/08 09:21:09, phoglund wrote:
> On 2016/11/08 09:18:29, commit-bot: I haz the power wrote:
> > CQ is trying da patch. Follow status at
> >  
> >
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
> 
> Or wait actually, that build was from yesterday. Let me investigate a bit
> more...

Nope,
https://build.chromium.org/p/chromium.webrtc/builders/Win10%20Tester/builds/1...
failed very recently, so I'm submitting this.

[phoglund, 2016-11-08 13:30:26]

The CQ bit was checked by phoglund@webrtc.org

[commit-bot: I haz the power, 2016-11-08 13:30:38]

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

[commit-bot: I haz the power, 2016-11-08 13:32:07]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-08 13:32:14]

Description was changed from

==========
Disabling NOTREACHED which we're hitting flakily in browser tests.

I have no idea how bad it is that we're hitting this limit; I'm just
doing this to stop the tests from flaking.

BUG=webrtc:6484
==========

to

==========
Disabling NOTREACHED which we're hitting flakily in browser tests.

I have no idea how bad it is that we're hitting this limit; I'm just
doing this to stop the tests from flaking.

BUG=webrtc:6484

Committed: https://crrev.com/6eaa55867b449df992752c1df540ec42f9d9b057
Cr-Commit-Position: refs/heads/master@{#14974}
==========

[commit-bot: I haz the power, 2016-11-08 13:32:16]

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

[åsapersson, 2016-12-19 07:30:32]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.webrtc.org/2585183002/ by asapersson@webrtc.org.

The reason for reverting is: To see if the NOTREACHED is still hit..