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
A couple of FactorGraph unit tests are buggy #1298
Comments
I have temporarily disabled these tests in #1311. |
@iglesias I'll fix ASAP. |
can we close this one? |
Sure. I'll take a look later today. On Tue, Feb 4, 2014 at 4:45 AM, Viktor Gal notifications@github.com wrote:
/**
|
@iglesias I tried valgrind --leak-check=full ./shogun-unit-test --gtest_filter=FactorGraph.evaluate_energy_param_data_* There is no problem on my laptop. Shall we close this? |
Sure, it looks fine! |
Valgrind detects quite a few errors for conditional jumps or moves depending on unitialised values in FactorGraph.evaluate_enery_param_data and FactorGraph.evaluate_enery_param_data_sparse, see output of
valgrind --leak-check=full ./shogun-unit-test --gtest_filter=FactorGraph.evaluate_energy_param_data_*
These tests are also leaking memory.
@hushell, let's try to fix this :)
The text was updated successfully, but these errors were encountered: