Fix VS 2015 Update 3, 14393 SDK landmine

Fix VS 2015 Update 3, 14393 SDK landmine

The VS 2015 Update 3, 14393 SDK landmine currently fires if you move to
building with VS 2017. That is undesirable. For local builds it is
unnecessary. For bot builds we need to fix the long-standing bug whereby
Windows compiler changes fail to trigger builds, rather than relying on
this landmine quirk.

R=scottmg@chromium.org
BUG=683729
Review-Url: https://codereview.chromium.org/2742603002
Cr-Commit-Position: refs/heads/master@{#455812}
Committed: https://chromium.googlesource.com/chromium/src/+/8f32820f092fb4b91778feb1304c6161fec14658

[brucedawson, 2017-03-09 00:31:19]

Description was changed from

==========
Fix VS 2015 Update 3 landmine

The VS 2015 Update 3, 14393 SDK landmine currently fires if you move to
building with VS 2017. That is undesirable. For local builds it is
unnecessary. For bot builds we need to fix the long-standing bug whereby
Windows compiler changes fail to trigger builds, rather than relying on
this landmine quirk.

R=scottmg@chromium.org
BUG=683729
==========

to

==========
Fix VS 2015 Update 3, 14393 SDK landmine

The VS 2015 Update 3, 14393 SDK landmine currently fires if you move to
building with VS 2017. That is undesirable. For local builds it is
unnecessary. For bot builds we need to fix the long-standing bug whereby
Windows compiler changes fail to trigger builds, rather than relying on
this landmine quirk.

R=scottmg@chromium.org
BUG=683729
==========

[brucedawson, 2017-03-09 00:31:30]

PTAL. Avoiding clobbers is a good thing.

[scottmg, 2017-03-09 00:48:32]

lgtm

[brucedawson, 2017-03-09 00:55:59]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2017-03-09 00:57:02]

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, 2017-03-09 01:53:54]

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

[commit-bot: I haz the power, 2017-03-09 01:53:55]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[brucedawson, 2017-03-09 01:58:51]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2017-03-09 01:59: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, 2017-03-09 02:57:56]

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

[commit-bot: I haz the power, 2017-03-09 02:57:57]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[brucedawson, 2017-03-09 18:14:34]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2017-03-09 18:14:57]

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, 2017-03-09 18:49:41]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489083274080000, "parent_rev":
"e8032e7dc308c5d6c530643af958bf942b8b831d", "commit_rev":
"8f32820f092fb4b91778feb1304c6161fec14658"}

[commit-bot: I haz the power, 2017-03-09 18:50:20]

Description was changed from

==========
Fix VS 2015 Update 3, 14393 SDK landmine

The VS 2015 Update 3, 14393 SDK landmine currently fires if you move to
building with VS 2017. That is undesirable. For local builds it is
unnecessary. For bot builds we need to fix the long-standing bug whereby
Windows compiler changes fail to trigger builds, rather than relying on
this landmine quirk.

R=scottmg@chromium.org
BUG=683729
==========

to

==========
Fix VS 2015 Update 3, 14393 SDK landmine

The VS 2015 Update 3, 14393 SDK landmine currently fires if you move to
building with VS 2017. That is undesirable. For local builds it is
unnecessary. For bot builds we need to fix the long-standing bug whereby
Windows compiler changes fail to trigger builds, rather than relying on
this landmine quirk.

R=scottmg@chromium.org
BUG=683729

Review-Url: https://codereview.chromium.org/2742603002
Cr-Commit-Position: refs/heads/master@{#455812}
Committed:
https://chromium.googlesource.com/chromium/src/+/8f32820f092fb4b91778feb1304c...
==========

[commit-bot: I haz the power, 2017-03-09 18:50:21]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/8f32820f092fb4b91778feb1304c...