-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-44976: [C++] Enable mimalloc by default, disable jemalloc by default and more #44951
Conversation
Not sure this is really minor, or if we want to create separate issues per individual change (though that may be overkill). Thoughts @kou ? |
compute/util.cc | ||
compute/util_internal.cc) |
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.
Those two files may be moved into the row
subdir perhaps.
@github-actions crossbow submit -g cpp |
This comment was marked as outdated.
This comment was marked as outdated.
Could you open at least one issue for this? |
|
1) Disable jemalloc by default 2) Enable mimalloc by default 3) Disable more compute modules by default
@github-actions crossbow submit -g cpp |
This comment was marked as outdated.
This comment was marked as outdated.
@github-actions crossbow submit -g cpp |
Revision: 709e86b Submitted crossbow builds: ursacomputing/crossbow @ actions-ffd8ebc12b |
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.
+1
The minimal build nightly tests seem to be failing because of this, see eg https://github.com/ursacomputing/crossbow/actions/runs/12279407480/job/34263376592 |
Ah, yes, indeed. It should be a quick fix if anyone is available before I am :) |
`test_memory.py` has started failing on some builds after apache#44951 was merged
I submitted #45007 to fix the Python CI failures. |
`test_memory.py` has started failing on some builds after apache#44951 was merged
`test_memory.py` has started failing on some builds after #44951 was merged * GitHub Issue: #45006 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
What changes are included in this PR?
arrow/compute
are only required when ARROW_COMPUTE is enabled, so we needn't compile them by defaultAre these changes tested?
Yes, by existing CI tests.
Are there any user-facing changes?
Yes, but nothing compatibility-breaking.