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/
< rcurtin> zoq: it was a long long day :(
< rcurtin> boost serialization is a nightmare to debug because the backtraces get so deep
< rcurtin> hundreds of stack frames...
govg has joined #mlpack
govg has quit [Ping timeout: 256 seconds]
govg has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#460 (master - 095844b : marcus): The build passed.
travis-ci has left #mlpack []
kirizaki has joined #mlpack
kirizaki has quit [Ping timeout: 240 seconds]
kirizaki has joined #mlpack
kirizaki has quit [Ping timeout: 260 seconds]
kirizaki has joined #mlpack
govg has quit [Ping timeout: 250 seconds]
govg has joined #mlpack
kirizaki has quit [Quit: Konversation terminated!]
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#461 (master - 3f79fab : Ryan Curtin): The build was broken.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#462 (master - 805789a : Ryan Curtin): The build was fixed.
travis-ci has left #mlpack []
< rcurtin> zoq: unfortunately I have to take down the build server and associated computers today
< rcurtin> I'll set up big and shoeshine and maybe one or two others at home temporarily
< rcurtin> I'm trying to get Symantec to let the big build server they got be accessible from externally, but I haven't had success yet
< zoq> rcurtin: oh okay, I guess there are a lot of security policies which makes everything much harder.
< rcurtin> the hardest part seems to be finding the right people to talk to :(