-
Notifications
You must be signed in to change notification settings - Fork 117
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
Building Failure on benchmark #444
Comments
Hi, I would like to take this issue on. Looking at the API, I can see that there is a partitionGraph member function under the Partitioner class here Perhaps the object from where this member function is called needs to be a Partitioner and not a Graph - should I change the Partition_BM.cpp file to incorporate this, or should I have the Graph class have a partitionGraph member function too ? Or am I missing something here ? Fwiw, The partition test calls the function from the Partitioner class. I am inclined towards doing it that way here too, let me know if I am missing something here though |
I Think your analysis is good, you can go on! |
Thank you! The build is working on my end, but I am running into a segmentation fault with the BFS benchmark when I run the benchmark_exe executable.
Haven't begun debugging as to why the Segmentation fault is happening, will take a look in some time. Is this to be raised as a new issue ? |
look at Memory consumption, it's possibile that you ram is full |
Thank you for the suggestion. I think I found why it was happening - I was running the benchmark executable from the wrong directory, so the cit_graph_ptr was nullptr. When I run it from the build directory, it works fine. I can make a PR for the original issue in some time :) |
good! |
Hi, I made a PR here. Please let me know if any changes are necessary and I can make them. Thank you for all your help! |
@ZigRazor This can be closed right? |
yes, this is closed by #445 |
We have the following problem with benchmark compilation, and the CI/CD fails:
The text was updated successfully, but these errors were encountered: