|
|
Chromium Code Reviews
DescriptionExplicitly set is_clang=true on the lkgr win asan bots
In the gyp build, asan=1 implicitly enabled clang. This should probably happen
in the gn build as well, but currently it doesn't. Until it does, explicitly
set it on these bots.
Thanks to etienneb@ for spotting this.
BUG=598761
R=etienneb@chromium.org, inferno@chromium.org
Committed: https://crrev.com/b2efa2c67908541d5a1a302283b1a675bf81902b
Cr-Commit-Position: refs/heads/master@{#409866}
Patch Set 1 #
Messages
Total messages: 19 (10 generated)
Description was changed from ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. BUG=598761 ========== to ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. Thanks to etienneb@ for spotting this. BUG=598761 ==========
thakis@chromium.org changed reviewers: + etienneb@chromium.org
The CQ bit was checked by thakis@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by thakis@chromium.org
The CQ bit was checked by thakis@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
inferno@chromium.org changed reviewers: + inferno@chromium.org
lgtm.
Description was changed from ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. Thanks to etienneb@ for spotting this. BUG=598761 ========== to ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. Thanks to etienneb@ for spotting this. BUG=598761 R=etienneb@chromium.org, inferno@chromium.org ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) to pending queue manually as c9101d13c3dbf27011de99cdc32d49e8061a64b9 (presubmit successful).
Message was sent while issue was closed.
Description was changed from ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. Thanks to etienneb@ for spotting this. BUG=598761 R=etienneb@chromium.org, inferno@chromium.org ========== to ========== Explicitly set is_clang=true on the lkgr win asan bots In the gyp build, asan=1 implicitly enabled clang. This should probably happen in the gn build as well, but currently it doesn't. Until it does, explicitly set it on these bots. Thanks to etienneb@ for spotting this. BUG=598761 R=etienneb@chromium.org, inferno@chromium.org Committed: https://crrev.com/b2efa2c67908541d5a1a302283b1a675bf81902b Cr-Commit-Position: refs/heads/master@{#409866} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/b2efa2c67908541d5a1a302283b1a675bf81902b Cr-Commit-Position: refs/heads/master@{#409866}
Message was sent while issue was closed.
dpranke@chromium.org changed reviewers: + dpranke@chromium.org
Message was sent while issue was closed.
Ah, whoops, good catch. +brettw for context ... We can't easily make is_clang=true when is_asan==true in the GN build, because is_clang is an arg declared in BUILDCONFIG.gn, and is_asan is declared in sanitizers.gni. We are trying to keep all of the sanitizer-related settings out of BUILDCONFIG.gn, but that means we end up with some limitations as a result ...
Message was sent while issue was closed.
On 2016/08/04 19:36:54, Dirk Pranke wrote: > Ah, whoops, good catch. > > +brettw for context ... > > We can't easily make is_clang=true when is_asan==true in the GN build, because > is_clang is an arg declared in BUILDCONFIG.gn, and is_asan is declared in > sanitizers.gni. We are trying to keep all of the sanitizer-related settings out > of BUILDCONFIG.gn, but that means we end up with some limitations as a result > ... In such cases I think the best thing is an assert in the sanitizer setup that makes sure the current combination of flags is reasonable.
Message was sent while issue was closed.
On 2016/08/04 22:14:13, brettw (ping on IM after 24h) wrote: > On 2016/08/04 19:36:54, Dirk Pranke wrote: > > Ah, whoops, good catch. > > > > +brettw for context ... > > > > We can't easily make is_clang=true when is_asan==true in the GN build, because > > is_clang is an arg declared in BUILDCONFIG.gn, and is_asan is declared in > > sanitizers.gni. We are trying to keep all of the sanitizer-related settings > out > > of BUILDCONFIG.gn, but that means we end up with some limitations as a result > > ... > > In such cases I think the best thing is an assert in the sanitizer setup that > makes sure the current combination of flags is reasonable. Yeah we have an assert, but it's still more awkward to use than previously. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
