ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
ulquiorra has joined #mlpack
petris has quit [Ping timeout: 265 seconds]
petris has joined #mlpack
ImQ009 has joined #mlpack
The_LoudSpeaker has quit [Quit: Leaving bye!]
The_LoudSpeaker has joined #mlpack
The_LoudSpeaker has quit [Quit: Leaving bye!]
The_LoudSpeaker has joined #mlpack
< walragatver[m]>
jeffin143: I am currently reviewing the PRs. So let's skip the meet for today
PileOfDirt has quit [Ping timeout: 260 seconds]
PileOfDirt has joined #mlpack
ulquiorra has quit [Quit: ulquiorra]
< jeffin143[m]>
Ok
< jeffin143[m]>
<walragatver[m] "jeffin143: I am currently review"> walragatver:
< jeffin143[m]>
> jeffin143: sounds good; I started talking about releasing mlpack 3.4.0 a while back so I should make sure to actually do it :)
< jeffin143[m]>
Gave a commit can you quickly take a loom
< jeffin143[m]>
If yoh have the bandwidth
< rcurtin>
jeffin143[m]: thanks, I will review it in a few hours :)
ImQ009 has quit [Quit: Leaving]
< shrit[m]>
rcurtin I am here
< shrit[m]>
I am not sure if these errors are related to serialization, for example, the errors of `GaussianDistribution`. The values before and after serialization seems to be the same, and the error is originated before the serialization process, you can comment the 470~473 and 507~510, and the test goes fine.
< shrit[m]>
test
< rcurtin>
shrit[m]: sorry, I did not see this, had some intense meetings
< rcurtin>
clearly the test passes before the cereal changes, so something must be different
< rcurtin>
it's also possible that the memory error is actually causing some other failures
< rcurtin>
for instance, you could try running the test in valgrind to see if anything is happening that is invalid (be sure to specify the test suite and test name there... valgrind on the whole test suite takes forever)
< rcurtin>
shrit[m]: when I run `bin/mlpack_test -t DistributionTest` locally, I have no failures
< rcurtin>
my guess, then is that solving the RectangleTree test is likely to solve the issue you are seeing with DistributionTest