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/
benchmark has quit [Read error: Connection reset by peer]
benchmark has joined #mlpack
benchmark has quit [Remote host closed the connection]
benchmark has joined #mlpack
benchmark has quit [Remote host closed the connection]
benchmark has joined #mlpack
benchmark has quit [Client Quit]
kshitijk has quit [Ping timeout: 246 seconds]
benchmark has joined #mlpack
benchmark has quit [Client Quit]
kshitijk has joined #mlpack
trapz has joined #mlpack
< naywhayare>
whoa, neat, jenkins now tells us the updated benchmarks?
kshitijk has quit [Ping timeout: 256 seconds]
< zoq>
naywhayare: yeah, I forgot to activate the feature, but now here it is
< naywhayare>
this is a cool feature... so, the number on the left is yesterday's benchmark run, and the number on the right is today's?
< zoq>
actually it's an independent database, but I think it would be great to use the daily benchmark database, I'll change that ... so every time someone makes a commit, the script checks if we should/can run a benchmark and posts the old value against the new value ... yesterday you refactored FastMKS to allow sparse dataset, so we get the results for the FastMKS benchmark, directly after the build finished
< naywhayare>
ah, okay
< naywhayare>
the daily database can be found on cabbie... /home/jenkins/workspace/benchmark-mlpack/reports/benchmark-daily.db
< naywhayare>
but the set of tests that gets run there is smaller
kshitijk has joined #mlpack
< zoq>
yeah, the daily benchmark takes 13 hours instead of weeks ...
govg has quit [Quit: leaving]
govg has joined #mlpack
kshitijk has quit [Ping timeout: 244 seconds]
< zoq>
naywhayare: Maybe we should do the same in log.cpp line 128?
< naywhayare>
ah, yeah, assert should throw an exception too