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/
xiaohong has joined #mlpack
xiaohong has quit [Remote host closed the connection]
xiaohong has joined #mlpack
xiaohong has quit [Ping timeout: 245 seconds]
xiaohong has joined #mlpack
xiaohong has quit [Remote host closed the connection]
< akhandait[m]>
zoq: Sorry for the late response. Here is the complete error message. Almost all of the errors seem to be with `STBI_` variables in core/data/ files. I hope that's helpful, if not I will post my build configuration.
< akhandait[m]>
I am using the latest ensmallen and armadillo 8.600.0
< akhandait[m]>
Though I don't think the above two have anything to do with these errors
Anmol has joined #mlpack
< Anmol>
Hello Everyone, I am new to open source community and I came across MLpack recently! I wish to contribute for it! Can anyone help me for how to get started?
< zoq>
Does anybody have any problem if we switch from Travis to azure pipelines, that should resolve the regular build timeout?
< ShikharJ>
zoq: I don't have one, but is Azure scheduling available for free?
< zoq>
ShikharJ: 10 parallel jobs with unlimited minutes per month for open source projects, so quite similar to Travis; each job can run for 240 minutes, but I think you have an option to bump the time.
< zoq>
It integrates quite well with Github, especially if you have Github actions, and as long as Microsft owns Github I think it will improve over the years.
< ShikharJ>
zoq: Wow, I didn't know any of that, I don't think of a reason why we shouldn't try that out.
< zoq>
ShikharJ: Well, MS doesn't have a positive record of supporting FOSS, so there might be some reservations.
travis-ci has joined #mlpack
< travis-ci>
mlpack/mlpack#8075 (master - 24bbbab : Marcus Edel): The build has errored.
ShikharJ__ has quit [Read error: Connection reset by peer]
ShikharJ has joined #mlpack
ShikharJ has quit [Ping timeout: 240 seconds]
< rcurtin>
zoq: sounds good to me; personally I'm a bit disappointed about how long the xenial support took with travis
< rcurtin>
but it's a bit strange to think that maybe the days of travis being totally standard might be coming to a close
< rcurtin>
it makes sense for Microsoft to push Azure since they bought Github though, I guess...
< rcurtin>
if you want to set it up I will be interested to see how it works :)
< zoq>
Especially for appveyor, this is must be difficult.
< rcurtin>
does azure do windows builds too? I guess I assume so?
< rcurtin>
I'm quite happy with AppVeyor's level of support; I suppose we could try switching if you like, but if it's extra work, I haven't seen any need
< zoq>
rcurtin: Yes, Linux, Windows, Mac OS
< rcurtin>
their VS2019 image isn't ready yet (I think this is why it times out regularly) but otherwise I haven't seen any issues
< zoq>
rcurtin: I think it would be nice to run the tests on windows as well.
< zoq>
But if I remember right we run into a timeout as well.
< rcurtin>
zoq: ah, good point, if Azure lets us run those too then maybe it is better to switch