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/
mikeling has joined #mlpack
chenzhe has quit [Ping timeout: 240 seconds]
chenzhe has joined #mlpack
chenzhe has quit [Ping timeout: 260 seconds]
mentekid has quit [Ping timeout: 245 seconds]
mentekid has joined #mlpack
vivekp has quit [Ping timeout: 272 seconds]
vivekp has joined #mlpack
govg has quit [Ping timeout: 255 seconds]
chenzhe has joined #mlpack
chenzhe has quit [Ping timeout: 246 seconds]
aashay has joined #mlpack
govg has joined #mlpack
govg has quit [Ping timeout: 272 seconds]
mentekid has quit [Quit: Leaving.]
< rcurtin>
the matrix build is almost fully working, finally :)
< zoq>
rcurtin: nice, almost?
< rcurtin>
yeah, it looks like there are a couple of build failures
< rcurtin>
and it also takes longer than 24 hours so it falls behind
< rcurtin>
the sparc64 systems are a lot slower to build mlpack than I would have thought
< rcurtin>
18 hours to run the tests in debug mode, 3.5 hours without debugging symbols, still very long
< zoq>
hm, 18 hours that's really long
< rcurtin>
yeah, it seems either the performance of the sparc64 processor is not good, or there are many tests that could be shortened (or both)
< zoq>
rcurtin: right, I'll have to take a deeper look into the recurrent network test, sometimes it takes a lot of time.
aashay has quit [Quit: Connection closed for inactivity]
mentekid has joined #mlpack
shikhar has joined #mlpack
chenzhe has joined #mlpack
shikhar has quit [Ping timeout: 260 seconds]
chenzhe has quit [Ping timeout: 268 seconds]
mikeling has quit [Quit: Connection closed for inactivity]
sheogorath27 has quit [Remote host closed the connection]