win 2015: Update the toolchain package to VS2015 RTM.

win 2015: Update the toolchain package to VS2015 RTM.

I've tried it locally (build Chrome with this archive on a fresh VM) and it worked well, the archive has been generated with package_from_installed.py (from depot_tools/win_toolchain)

BUG=440500
Committed: https://crrev.com/f04ff85d2b85833971ef7ca7f31f4fd5a1b1f3aa
Cr-Commit-Position: refs/heads/master@{#340898}

Committed: https://crrev.com/21f280ff2c7838a748b7aa93391164fcd185d53b
Cr-Commit-Position: refs/heads/master@{#341146}

[Sébastien Marchand, 2015-07-28 20:40:42]

sebmarchand@chromium.org changed reviewers:
+ brucedawson@chromium.org

[Sébastien Marchand, 2015-07-28 20:40:42]

PTAL.

[Sébastien Marchand, 2015-07-28 20:43:49]

sebmarchand@chromium.org changed reviewers:
+ thakis@chromium.org

[Sébastien Marchand, 2015-07-28 20:43:50]

Just realized that you're not an owner for this, +thakis@ for owner approval.

[Nico, 2015-07-28 20:45:12]

is https://code.google.com/p/chromium/issues/detail?id=498544 fixed?

[Sébastien Marchand, 2015-07-28 20:48:54]

I don't know, I'll check locally and I'll let you know

[Sébastien Marchand, 2015-07-28 20:53:08]

I don't think that this bug should prevent us from switching from the RC to the
RTM, we just won't switch the default toolchain to VS2015.

[Nico, 2015-07-28 20:53:46]

Ah right. lgtm then.

[Sébastien Marchand, 2015-07-29 16:32:22]

The CQ bit was checked by sebmarchand@chromium.org

[Sébastien Marchand, 2015-07-29 16:32:22]

The patchset sent to the CQ was uploaded after l-g-t-m from thakis@chromium.org
Link to the patchset: https://codereview.chromium.org/1265503002/#ps20001
(title: " ")

[commit-bot: I haz the power, 2015-07-29 16:33:41]

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

[commit-bot: I haz the power, 2015-07-29 16:44:19]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-07-29 16:44:52]

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

[Sébastien Marchand, 2015-07-29 17:03:19]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/1254023004/ by sebmarchand@chromium.org.

The reason for reverting is: It's breaking the VS2015 builder. I'm looking at
it..

[Sébastien Marchand, 2015-07-30 17:14:17]

I've installed the VS2015 redistribuables on the bot, relanding this to fix the
debug builder.

[Sébastien Marchand, 2015-07-30 17:14:37]

The CQ bit was checked by sebmarchand@chromium.org

[commit-bot: I haz the power, 2015-07-30 17:15:21]

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

[commit-bot: I haz the power, 2015-07-30 17:24:50]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-07-30 17:25:33]

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

[brucedawson, 2015-08-03 18:47:05]

This should have had BUG=440500 in order to associate it with the VS 2015 bug -
I missed that earlier.

The debug builder is now failing for a different reason:
> Failed to find an input file: Input file
C:\b\build\slave\chromium-dbg-builder\build\src\out\Debug\msvcp120d.dll doesn't
exist

I'm going to put this information in the bug as well.

[scottmg, 2015-08-07 20:33:43]

On 2015/07/30 17:14:17, Sébastien Marchand wrote:
> I've installed the VS2015 redistribuables on the bot, relanding this to fix
the
> debug builder.

Ideally we wouldn't be installing redists on bots. I don't want to have to deal
with that on every new VM.