You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/05/14 17:55:00 UTC

[jira] [Resolved] (IMPALA-3492) buildall.sh should clean up after ASAN builds

     [ https://issues.apache.org/jira/browse/IMPALA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-3492.
-----------------------------------
    Resolution: Cannot Reproduce

This works for me now for a couple of years at least - I can run buildall.sh -noclean -asan ... and switch to/from ASAN with no problems.

> buildall.sh should clean up after ASAN builds
> ---------------------------------------------
>
>                 Key: IMPALA-3492
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3492
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 2.6.0
>            Reporter: Jim Apple
>            Priority: Minor
>
> Building with buildall.sh and the asan flag makes non-asan builds fail when using buildall.sh and noclean.
> There are some workarounds: do a clean build (but this kills third-party services), run bin/clean.sh, and 
> {noformat}
> find -iname '*cmake*' -not -name CMakeLists.txt | grep -v -e cmake_module | grep -v -e thirdparty | xargs rm -Rf
> {noformat}
> It would be best if buildall.sh just took care of this itself.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)