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/
govg has joined #mlpack
manish7294 has joined #mlpack
manish7294 has quit [Ping timeout: 276 seconds]
manish7294 has joined #mlpack
Chestnut has joined #mlpack
< Chestnut> K4k
Chestnut has quit [Client Quit]
daivik has joined #mlpack
manish7294 has quit [Ping timeout: 246 seconds]
manish7294 has joined #mlpack
manish7294 has quit [Ping timeout: 252 seconds]
govg has quit [Ping timeout: 252 seconds]
daivik has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
gaurav_ has joined #mlpack
Trion has joined #mlpack
vijay_ has joined #mlpack
vijay_ has quit [Client Quit]
< Trion> rcurtin: Got the mlpack stickers! ^_^ love them! They are my first laptop stickers too :) https://imgur.com/7tzF2Wx
ShikharJ has joined #mlpack
< rcurtin> Trion: great to hear that you like them :)
< ShikharJ> rcurtin: Does Travis have auto-cancellation of builds enabled for mlpack? I had pushed twice today, on the same branch and one of the processes still seems to be running.
ShikharJ has quit [Client Quit]
< rcurtin> ShikharJ: I think that you are right and travis does a lot of extra builds; maybe it could be reduced
mikeling has joined #mlpack
gaurav_ has quit [Ping timeout: 260 seconds]
ImQ009 has joined #mlpack
Trion has quit []
travis-ci has joined #mlpack
< travis-ci> ShikharJ/mlpack#49 (CrossEntropyLogit - ef78399 : Shikhar Jaiswal): The build has errored.
travis-ci has left #mlpack []
< zoq> ShikharJ: Good point, auto canceling is now enabled.
< rcurtin> zoq: thanks, I imagine the travis organization appreciates it too :)
kaushik_ has joined #mlpack
witness has joined #mlpack
daivik has joined #mlpack
daivik has left #mlpack []
jenkins-mlpack has quit [Remote host closed the connection]
jenkins-mlpack has joined #mlpack
< zoq> rcurtin: The failing memory test is my fault, I was tesing to somehow redirect the details to the results page.
< rcurtin> ahhh, ok
< rcurtin> I updated all the plugins and restarted, hopefully this causes no issues
< zoq> rcurtin: Should be fixed.
< zoq> okay
< rcurtin> I found someone else who had a similar problem and then I realized our plugins were out of date, so I thought I would try that first
< rcurtin> it doesn't seem like we have a good way to re-trigger a build on Jenkins; do you know a way?
< rcurtin> it seems like the only way is to push a change
< zoq> you can setup a trigger phrase for each job
< zoq> but I think the default is "test this" not sure
< zoq> I can look into this later today.
< zoq> It worked for the benchmark repo.
< rcurtin> oops, I wrote "build this", I thought that wasn't quite right
< rcurtin> I'll try in another PR, let's see...
< rcurtin> hm, doesn't look like it worked, but it any case I don't think it matters much
< zoq> right, normally there is no need for a restart
< rcurtin> ohh, I see, you have to say 'please' so that it actually restarts the jobs :)
< zoq> :)
witness has quit [Quit: Connection closed for inactivity]
mikeling has quit [Quit: Connection closed for inactivity]
ShikharJ has joined #mlpack
ShikharJ has quit [Ping timeout: 260 seconds]
kaushik_ has quit [Quit: Connection closed for inactivity]
ImQ009 has quit [Read error: Connection reset by peer]