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/
pbrunet has joined #mlpack
< zoq> I guess the travis build uses some time consuming starting seeds. Not sure how to fix the issue easily without remote control. At least the jenkins build works without any timeout problems :)
< naywhayare> I was thinking maybe we could compile on travis in non-debug mode, and that would make the tests faster
< naywhayare> but that might make debugging failed travis builds harder... it's at least a decent first shot at a solution though :)
pbrunet has quit [Ping timeout: 244 seconds]
< zoq> naywhayare: yeah, maybe that works
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#210 (master - b34381d : Ryan Curtin): The build has errored.
travis-ci has left #mlpack []
< Rodya> naywhayare as long as the test output is clear about what test failed (and the tests aren't random), should be easy to repro locally
< Rodya> or if the tests are random it outputs a thing for you to jam into the test to make it do the same thing
< naywhayare> Rodya: that's true; also, the matrix build on Jenkins might be better for tracking down hard-to-reproduce issues (since it does so many builds)
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#211 (master - 7b68ca3 : Ryan Curtin): The build failed.
travis-ci has left #mlpack []