Skip to content
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

Test fails when built without debug or profiling #191

Closed
rcurtin opened this issue Dec 29, 2014 · 4 comments
Closed

Test fails when built without debug or profiling #191

rcurtin opened this issue Dec 29, 2014 · 4 comments
Assignees
Milestone

Comments

@rcurtin
Copy link
Member

rcurtin commented Dec 29, 2014

Reported by speet3 on 7 Aug 42087201 03:36 UTC
For full log, see output from http://hotwheels.cc.gt.atl.ga.us:8080/job/MLPACK_Debian_Package/99/console

Running 169 test cases...
/var/lib/jenkins/jobs/MLPACK_Debian_Package/workspace/build-area/mlpack-1.0.0/src/mlpack/tests/nca_test.cpp(93): fatal error in "SoftmaxInitialGradient": critical check gradient(1, 0) == 0.0 failed
[0;33m[WARN ] [determine type of file 'noextension'; no extension is present.  Load failed.
[0;33m[WARN ](0mCannot) [extension given with filename 'noextension'; type unknown.  Save failed.
[0;33m[WARN ](0mNo) [open file 'nonexistentfile_______________.csv'; load failed.
[0;33m[WARN ](0mCannot) [0mLoading 'test_file.bin' as raw binary formatted data; but this may not be the actual filetype!

I think this may possibly be related to how make calls the test, but I do not know. The previous build did not fail, and there was no change made to the mlpack code base. The only changes were made as a patch to the CMakeLists.txt, applied after the packaging unpacks the source and before building it. The patch was added in r11320.

@rcurtin rcurtin self-assigned this Dec 29, 2014
@rcurtin rcurtin added this to the mlpack 1.0.1 milestone Dec 29, 2014
@rcurtin rcurtin closed this as completed Dec 29, 2014
@rcurtin
Copy link
Member Author

rcurtin commented Dec 30, 2014

Commented by rcurtin on 12 Jan 42088365 21:48 UTC
Probably an uninitialized variable or something like that that only causes errors sometimes at compilation. I cannot reproduce it on my desktop; I'll try a few other systems.

@rcurtin
Copy link
Member Author

rcurtin commented Dec 30, 2014

Commented by speet3 on 28 Nov 42088712 05:48 UTC
You should still be able to login to hotwheels and try there. Also, I don't know why compiling without debug and profiling has nearly doubled the time to compile. Perhaps something important is incorrectly located in the debug templates?

@rcurtin
Copy link
Member Author

rcurtin commented Dec 30, 2014

Commented by rcurtin on 26 Nov 42088718 16:41 UTC
Probably because GCC is doing optimizations (just my guess). I'll log into hotwheels and poke around.

@rcurtin
Copy link
Member Author

rcurtin commented Dec 30, 2014

Commented by speet3 on 20 Apr 42091428 15:10 UTC
This ticket seems to have been resolved in r11340

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant