01:56 < jenkins-mlpack2> Project docker mlpack nightly build build #446: STILL UNSTABLE in 4 hr 46 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/446/

02:01 < rcurtin> still unstable! :( :( :(

02:12 < rcurtin> oh! I forgot. I have to run the "docker mlpack git checkout" job first. now I will start it all again...

02:12 < jenkins-mlpack2> Project docker mlpack weekly build build #69: ABORTED in 5 hr 2 min: http://ci.mlpack.org/job/docker%20mlpack%20weekly%20build/69/

02:13 < rcurtin> excess flood... oops

02:13 < rcurtin> I wonder what jenkins-mlpack2 was trying to say :)

06:13 < ShikharJ> rcurtin: MiniBatchDiscrimination PR is in, I think that atleast the layers functionality can be included in this release, we just need to leave out GANs and RBMs I think.

06:22 < ShikharJ> rcurtin: Ah, correction, we already released the RBMs, just GANs:)

06:48 < jenkins-mlpack2> Project docker mlpack nightly build build #447: STILL UNSTABLE in 4 hr 35 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/447/

10:46 < zoq> rcurtin: Looks like there is at least one test to fix.

11:28 < jenkins-mlpack2> Project docker mlpack weekly build build #70: STILL UNSTABLE in 9 hr 15 min: http://ci.mlpack.org/job/docker%20mlpack%20weekly%20build/70/

12:23 < jenkins-mlpack2> Project docker mlpack nightly build build #448: STILL UNSTABLE in 5 hr 34 min: http://ci.mlpack.org/job/docker%20mlpack%20nightly%20build/448/

12:51 < rcurtin> zoq: yeah, maybe a couple more

16:51 < rcurtin> ShikharJ: sounds good, I'll just remove the gan/ directory from the release if that sounds good to you (and the associated tests)

17:16 < lozhnikov> rcurtin: Looks like I didn't open the IRC app yesterday:) I think these PRs are still far from being ready. I hope we can finish them before the release after 3.2.0.

17:22 < rcurtin> lozhnikov: ok, sounds good---I will make sure that they are not in the critical path for the release :)

17:25 < lozhnikov> rcurtin: I think I can finish the PRs in a month. Unfortunately I spent the last month writing a report:(

17:25 < rcurtin> no worries :) there is no particular hurry

17:25 < rcurtin> hopefully the report came out well :)

17:29 < lozhnikov> No, the deadline moved to the end of October:(. So, I decided to put it aside, I don't want to spend the whole time on it. Improving a report can be an infinite process.

17:30 < rcurtin> it's true---"work expands to fill all allowable space" :)

17:36 < favre49> I just i realized I forgot to thank you all for the help during GSoC :) I hope I can continue to help out

17:38 < favre49> Some bad news is, NSGA-III will take some time, since pretty much all of my free time every day is tied up in robotics. Perhaps I've put my head into too many things this semester.

17:39 < favre49> Another issue is there is only one working implementation, so testing and debugging is very slow. I've been chipping away at it very slowly though

17:41 < favre49> Also, this is unrelated to mlpack, but I remember recommending Sublime Text 3, and i found it does not display all the files in a directory :) Was quite annoying, since I was looking for an sdf file and a .so file. Back to VSCode, I guess.

17:48 < zoq> favre49: I had a lot of fun during the summer, and I look forward to use NEAT on the next project.

17:48 < zoq> favre49: Finding time is always challenging, my list of things I like to do grows from day to day.

20:15 < rcurtin> favre49: it was awesome that you were a student this year; I hope that you can find some time to continue participating :)

20:16 < rcurtin> I know how you feel about the free time... I think we are all juggling a lot of different things and only fit in mlpack when we can :)

20:58 < jenkins-mlpack2> Yippee, build fixed!

20:58 < jenkins-mlpack2> Project docker ensmallen nightly build » armadillo-8.600.1,llvm-8.0.1,docker build #4: FIXED in 3 min 59 sec: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/armadillo_version=armadillo-8.600.1,compiler_version=llvm-8.0.1,label=docker/4/

20:58 < jenkins-mlpack2> Yippee, build fixed!

20:58 < jenkins-mlpack2> Project docker ensmallen nightly build » armadillo-9.100.6,llvm-8.0.1,docker build #4: FIXED in 4 min 3 sec: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/armadillo_version=armadillo-9.100.6,compiler_version=llvm-8.0.1,label=docker/4/

20:58 < jenkins-mlpack2> Yippee, build fixed!

20:58 < jenkins-mlpack2> Project docker ensmallen nightly build » armadillo-9.600.6,llvm-8.0.1,docker build #4: FIXED in 4 min 11 sec: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/armadillo_version=armadillo-9.600.6,compiler_version=llvm-8.0.1,label=docker/4/

20:58 < jenkins-mlpack2> Yippee, build fixed!

20:58 < jenkins-mlpack2> Project docker ensmallen nightly build » armadillo-9.400.4,llvm-8.0.1,docker build #4: FIXED in 4 min 17 sec: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/armadillo_version=armadillo-9.400.4,compiler_version=llvm-8.0.1,label=docker/4/

21:18 < rcurtin> four minute builds... so different than mlpack :D

21:18 < zoq> only the build step

21:19 < rcurtin> ah, fair enough

21:19 < zoq> but about 15min with tests

21:19 < rcurtin> still much shorter than mlpack :)

21:19 < zoq> true

21:43 < jenkins-mlpack2> Project docker ensmallen nightly build build #5: ABORTED in 39 min: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/5/

22:33 < jenkins-mlpack2> Project docker ensmallen nightly build build #6: ABORTED in 50 min: http://ci.mlpack.org/job/docker%20ensmallen%20nightly%20build/6/