-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](memory) Fix build.sh thirdparty path error for jemalloc #34643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
morningman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
TeamCity be ut coverage result: |
|
run buildall |
03fbab5 to
c9416a7
Compare
|
run buildall |
|
TeamCity be ut coverage result: |
|
PR approved by at least one committer and no changes requested. |
morningman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…#34643) Fix build.sh thirdparty path error for jemalloc fix jemalloc thirdparty is compatible with old code if build_type=ASAN, compile without jemalloc, because asan not compatible with jemalloc without prefix Crash only with Jemalloc, ASan is clean jemalloc/jemalloc#2353
…#34643) Fix build.sh thirdparty path error for jemalloc fix jemalloc thirdparty is compatible with old code if build_type=ASAN, compile without jemalloc, because asan not compatible with jemalloc without prefix Crash only with Jemalloc, ASan is clean jemalloc/jemalloc#2353
…apache#34643)" This reverts commit 875b85c.
…apache#34643)" This reverts commit 875b85c.
Proposed changes
Crash only with Jemalloc, ASan is clean jemalloc/jemalloc#2353
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...