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/
sumedhghaisas3 has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 256 seconds]
sumedhghaisas3 has quit [Read error: Connection reset by peer]
sumedhghaisas2 has joined #mlpack
vivekp has quit [Ping timeout: 260 seconds]
vivekp has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#3 (Patch - 3bd4acf : Manish): The build failed.
< travis-ci> Change view : https://github.com/manish7294/mlpack/compare/a419476dbee8^...3bd4acfdf3c3
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#68 (Patch - 3bd4acf : Manish): The build failed.
< travis-ci> Change view : https://github.com/manish7294/mlpack/compare/a419476dbee8^...3bd4acfdf3c3
travis-ci has left #mlpack []
vivekp has quit [Ping timeout: 240 seconds]
vivekp has joined #mlpack
lozhnikov has joined #mlpack
sumedhghaisas3 has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 245 seconds]
sumedhghaisas3 has quit [Read error: Connection reset by peer]
sumedhghaisas2 has joined #mlpack
vpal has joined #mlpack
vivekp has quit [Ping timeout: 245 seconds]
vpal is now known as vivekp
< jenkins-mlpack2> Yippee, build fixed!
< jenkins-mlpack2> Project docker mlpack nightly build build #11: FIXED in 6 hr 7 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/11/
< rcurtin> I'm still waiting to hear back about masterblaster and the other systems
< rcurtin> I'm wondering if a month or more is going to go by before anything comes back
< rcurtin> I suppose it's also possible they may just shut them down with no notification, but I have no visibility into the process
< zoq> rcurtin: Probably not the best idea to start a new benchmark at this time.
< rcurtin> I think I will do it anyway, the worst case is just that we don't get complete results :)
< rcurtin> if they do eventually shut them down we have to redo all the benchmarks with new systems anyway...
< zoq> okay, sounds reasonable
ImQ009 has joined #mlpack
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#4 (impBounds - 42303c3 : Manish Kumar): The build failed.
travis-ci has left #mlpack []
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#69 (impBounds - 42303c3 : Manish Kumar): The build is still failing.
travis-ci has left #mlpack []
sumedhghaisas3 has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 276 seconds]
sumedhghaisas2 has joined #mlpack
sumedhghaisas3 has quit [Ping timeout: 276 seconds]
vivekp has quit [Read error: Connection reset by peer]
vpal has joined #mlpack
vpal is now known as vivekp
sumedhghaisas2 has quit [Read error: Connection reset by peer]
sumedhghaisas2 has joined #mlpack
sumedhghaisas2 has quit [Ping timeout: 240 seconds]
< Atharva> zoq: Did you get time to look at the code I mailed you?
< Atharva> rcurtin: Are you there?
< Atharva> Okay I will ask my doubt for whenever someone becomes free.
< Atharva> I added ${Boost_Serialization_LIBRARIES} in target_link_libraries of the vae folder in models repo. I still get collect2: error: ld returned 1 exit status when building it.
< zoq> Atharva: hm, https://github.com/mlpack/models/blob/master/CMakeLists.txt#L147-L151 should cover the boost lib part. Can you push the latest changes to the models repo? I can see if I get the same issue.
< zoq> Atharva: About the code, yes, I can at least reproduce the 'issue'.
< Atharva> zoq: I will push the latest changes to the PR
travis-ci has joined #mlpack
< travis-ci> manish7294/mlpack#5 (impBounds - f972da4 : Manish): The build is still failing.
travis-ci has left #mlpack []
< Atharva> zoq: I have updated the PR with the CMakeLists.txt file
< zoq> Atharva: Okay, see my comment on the PR, let me know if that solves the issue.
< Atharva> It worked, thanks!
< zoq> Great :)
ImQ009 has quit [Quit: Leaving]