verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
vivekp has quit [Ping timeout: 240 seconds]
vivekp has joined #mlpack
mikeling has joined #mlpack
< rcurtin>
mikeling: have you had a chance to add the test for the weighted decision tree learning that I suggested?
< rcurtin>
I was hoping to look into that tomorrow, so if you haven't, no worries, I just wanted to avoid duplicating work if possible :)
mikeling has quit [Quit: Connection closed for inactivity]
< jenkins-mlpack>
Marcus Edel: Define the model for each init rule to fix gcc issue.
benchmark has joined #mlpack
benchmark has quit [Client Quit]
< rcurtin>
wow, that's really fast, it took -2 seconds to run...
< zoq>
yeah :) I forgot to map the error for the IRC message ...
< rcurtin>
I guess, for the matlab search path, I would have to add every methods/*/ directory, does that seem right to you?
< zoq>
yeah, export MATLABPATH=$(shell pwd)/methods/matlab/ should do
< rcurtin>
oh, right
< rcurtin>
I should have checked...
< rcurtin>
for some reason I thought it was laid out like mlpack where each method had its own directory :)
< rcurtin>
now we can wait for a long time to see if I fixed the issues, since the checkout job now takes a couple hours because it builds all the libraries
< rcurtin>
I guess, I could do the build step in parallel
< zoq>
yeah, I guess you could run it in parallel
< rcurtin>
yeah, I am changing the scripts now
< zoq>
but I don't mind to wait :)
< rcurtin>
ok, that should work better now, we can save some time :)
mikeling has quit [Quit: Connection closed for inactivity]
< zoq>
right, just use all cores to build the libs
chenzhe has joined #mlpack
chenzhe has quit [Ping timeout: 272 seconds]
chenzhe has joined #mlpack
chenzhe has quit [Ping timeout: 272 seconds]
chenzhe has joined #mlpack
chenzhe has quit [Ping timeout: 240 seconds]
vinayakvivek has quit [Quit: Connection closed for inactivity]
< rcurtin>
weird, a segmentation fault in the python xml unittest runner...
< zoq>
yeah, weird haven't found a solution yet, just a "workaround"
< rcurtin>
oh, do you have a workaround for it?
< rcurtin>
I was still trying to narrow down the cause
< rcurtin>
it seems like the test XMLs are generated anyway, but maybe there is a problem with one of them, I haven't checked fully
< zoq>
workaround is probably not the right term, since jenkins fails I used 'make checks || mkdir -p test' that way the build passes and the status depends on the number of failed tests, definitely not the best solution
< rcurtin>
I think that's an ok workaround for now