-
Notifications
You must be signed in to change notification settings - Fork 5
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
dataset-serialize
benchmark is failing with segfaults
#166
dataset-serialize
benchmark is failing with segfaults
#166
Comments
The only machine that runs this is
Interestingly, sometimes one or two cases succeed before the segfault, and sometimes none of them do. |
Here's a breakdown of the number of successful
|
The first run without 24 results was this one: On commit apache/arrow@d7017dd, which has the message |
dataset-serialize
benchmark is failingdataset-serialize
benchmark is failing with segfaults
@jorisvandenbossche It looks like the |
We could probably just set I think it depends on what the Arrow community wants to actually be measuring here. For instance, it may not make sense to compare the benchmark timings measured with and without |
We could do that short-term to get the benchmark working again. The benchmark is actually about writing if I am reading it correctly, and so it segfaults in the setup, thus changing this won't impact the actual benchmark. (although it is a bit strange that it still logs the timing info after reading) But the change that started this ( We did have some crashes on the main Arrow CI as well after merging that PR, but those were fixed with apache/arrow#38073 |
Okay, I opened apache/arrow#38438. I'll try to see if using |
I was able to avoid the segfault locally by setting Like you said though, apache/arrow#38438 seems like a critical bug. |
That band-aid worked: https://buildkite.com/apache-arrow/arrow-bci-benchmark-on-ursa-i9-9960x/builds/3689#018b64a3-2deb-4824-96ee-3b13c7c67261/6-24113
|
Thanks for opening the issue! Will try to further look into that tomorrow. |
I've try to fix it here: apache/arrow#38466 Not sure this really fix the bug, you can have a try here... |
More details to come.
The text was updated successfully, but these errors were encountered: