Add rtc_include_tests to override; WebRTC will require that shortly.

Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
Committed: https://crrev.com/586733f102a9656ea0302816bcbe375f43165681
Cr-Commit-Position: refs/heads/master@{#406329}

[phoglund_chromium, 2016-07-18 15:10:04]

phoglund@chromium.org changed reviewers:
+ brettw@chromium.org

[brettw, 2016-07-18 17:54:09]

See my comment on the bug.

[phoglund_chromium, 2016-07-19 10:59:35]

Description was changed from

==========
Explicitly override WebRTC rtc_include_tests setting.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
==========

to

==========
Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
==========

[phoglund_chromium, 2016-07-19 10:59:49]

Changed title to reflect discussion in bug; PTAL

[phoglund_chromium, 2016-07-19 14:16:27]

The CQ bit was checked by phoglund@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-19 14:17:00]

Dry run: 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-07-19 15:13:53]

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

[commit-bot: I haz the power, 2016-07-19 15:13:54]

Dry run: This issue passed the CQ dry run.

[brettw, 2016-07-19 17:42:46]

lgtm

[phoglund_chromium, 2016-07-19 18:28:24]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2016-07-19 18:28:59]

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-07-19 18:38:17]

Description was changed from

==========
Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
==========

to

==========
Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
==========

[commit-bot: I haz the power, 2016-07-19 18:38:19]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-19 18:39:39]

Description was changed from

==========
Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119
==========

to

==========
Add rtc_include_tests to override; WebRTC will require that shortly.

My current plan of attack is to flip rtc_include_tests over to true by
default and make Chrome explicitly set it to false. This means I must
land this change first and then the WebRTC change. This won't make
parity with the WebRTC .gyp files worse since they handle this
particular thing different anyway (.gyp files look at
build_with_chromium to make this decision, I believe).

BUG=webrtc:6119

Committed: https://crrev.com/586733f102a9656ea0302816bcbe375f43165681
Cr-Commit-Position: refs/heads/master@{#406329}
==========

[commit-bot: I haz the power, 2016-07-19 18:39:40]

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