|
|
Created:
5 years, 4 months ago by Sébastien Marchand Modified:
5 years, 4 months ago CC:
chromium-reviews, Dirk Pranke Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMake VS2015 component builds work on swarming.
BUG=440500
Committed: https://crrev.com/568e81bce0dbf53936edfb4d54a5714749a2e619
Cr-Commit-Position: refs/heads/master@{#343482}
Patch Set 1 #Patch Set 2 : Add an OS check. #Patch Set 3 : Move the msvs dependencies into their own isolate file. #Patch Set 4 : Update the Androit isolator script. #
Messages
Total messages: 35 (15 generated)
The CQ bit was checked by sebmarchand@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1252353005/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1252353005/1
sebmarchand@chromium.org changed reviewers: + brucedawson@chromium.org, thakis@chromium.org
PTAL
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
Lgtm once the bots like it. Not sure if gn needs anything like this.
dpranke@chromium.org changed reviewers: + dpranke@chromium.org
GN will probably need something similar at some point. So far we're only running static builds through swarming.
The CQ bit was checked by sebmarchand@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1252353005/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1252353005/20001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
It looks like the isolate file format doesn't allow for nested conditions and it doesn't do a left to right check of its conditions (i.e. "OS=="win" and msvs_version==2013" will fail if msvs_version even if OS!="win")... So I should either fix isolate.py, or provide a default value for msvs_version on all platforms... I don't really like this approach but it's probably the best short term fix...
Maybe rename it from msvs_version to compiler_version, which can be msvs_2013, msvs_2015, or gcc_47, etc.
yeah, but this might create some confusion too.. We'll introduce a global variable that will only be used on Windows, so 2 things can happen: - We'll set it to 0 on the platforms where it doesn't get used, and some people will wonder why there's a 'compiler_version=0' flag on the isolate.py command line. - We'll set it to the appropriate version on each platforms, and then we'll switch to gcc 4.8 and nobody will ever update this value. So there's no ideal solution here, we can maybe just wait for maruel@ to be back from vacation to see if isolate file format limitations are here on purpose or not, if not then the best way to fix this will probably be to add support for nested conditions or to implement left to right parsing of the conditions...
On 2015/08/04 21:16:36, Sébastien Marchand wrote: > yeah, but this might create some confusion too.. We'll introduce a global > variable that will only be used on Windows, so 2 things can happen: > - We'll set it to 0 on the platforms where it doesn't get used, and some people > will wonder why there's a 'compiler_version=0' flag on the isolate.py command > line. > - We'll set it to the appropriate version on each platforms, and then we'll > switch to gcc 4.8 and nobody will ever update this value. > > So there's no ideal solution here, we can maybe just wait for maruel@ to be back > from vacation to see if isolate file format limitations are here on purpose or > not, if not then the best way to fix this will probably be to add support for > nested conditions or to implement left to right parsing of the conditions... Can't we just map everything? It's not that much a big deal and simplifies everything. We can then revisit once fully switched to GN.
Nop we can't, the *140.dll files are present only if VS2015 has been downloaded (i.e. the dev has set GYP_MSVS_VERSION=2015).
Patchset #3 (id:40001) has been deleted
The CQ bit was checked by sebmarchand@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1252353005/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1252353005/60001
sebmarchand@chromium.org changed reviewers: + maruel@chromium.org
+maruel for the .isolate changes.
lgtm, thanks
The CQ bit was unchecked by sebmarchand@chromium.org
The CQ bit was checked by sebmarchand@chromium.org
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/1252353005/#ps60001 (title: "Move the msvs dependencies into their own isolate file.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1252353005/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1252353005/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_android_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_android_r...)
The CQ bit was checked by sebmarchand@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from thakis@chromium.org, maruel@chromium.org Link to the patchset: https://codereview.chromium.org/1252353005/#ps80001 (title: "Update the Androit isolator script.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1252353005/80001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1252353005/80001
Message was sent while issue was closed.
Committed patchset #4 (id:80001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/568e81bce0dbf53936edfb4d54a5714749a2e619 Cr-Commit-Position: refs/heads/master@{#343482} |