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/
< zoq> Sorry for the mail flooding.
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#196 (master - fd33623 : Marcus Edel): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#197 (master - 3413a77 : Marcus Edel): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#198 (master - 967adc4 : Marcus Edel): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#199 (master - 459b7fe : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#200 (master - be6fe1f : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#201 (master - f601eae : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#202 (master - f2758b2 : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#203 (master - 3375caa : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
< naywhayare> zoq: is it time to upgrade the minimum armadillo requirement? 3.800 has transform()
< naywhayare> might need to figure out how to update Travis to get a newer version of Armadillo
< zoq> We can use the standard for loop, there is another unsupported function 'vectorise()', I guess I can create a new object using the memptr to achieve the same result.
< zoq> I'll go and check if there is another function which isn't supported before doing anything else.
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#204 (master - ad4cc1b : Marcus Edel): The build passed.
travis-ci has left #mlpack []
< naywhayare> vectorise() is 3.910, we can bump the minimum required version to that
< naywhayare> I think Conrad was saying Armadillo 4 is available in most distributions
< naywhayare> 4.000.0 is a year and a half old already too, so that should be enough time for it to be available in most places :)
< zoq> That would be alot easier ... 3.6 is pretty old
< naywhayare> yeah, let's do that then
< naywhayare> I'm not sure exactly what will need to happen to the travis configuration, though
< zoq> I'll see what I can find out.
< zoq> I guess we can just install libarmadillo-dev libarmadillo4
< zoq> I'll go and test it on a ubuntu linaro system.
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#205 (master - 07f205f : Ryan Curtin): The build passed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#206 (master - 49d726c : Ryan Curtin): The build passed.
travis-ci has left #mlpack []
< zoq> naywhayare: okay, if you like I can make the necessary change
< naywhayare> sure, go ahead
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#207 (master - 4630d8d : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
< zoq> ...
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#208 (master - fbb25be : Marcus Edel): The build has errored.
travis-ci has left #mlpack []
< naywhayare> when the jenkins build finishes I'll try and see which test is taking so long
< zoq> hm, I guess we can just look at the last build because nothing changed except the travis config
< zoq> I don't see any test with a runtime > 3 minutes
< naywhayare> maybe it was just a bad random seed or something... give me a few moments to check in some more documentation to run travis again and let's see what happens...
travis-ci has joined #mlpack
< travis-ci> mlpack/mlpack#209 (master - fab25ea : ryan): The build has errored.
travis-ci has left #mlpack []