build failure emails are a desperate call for help from this community. I don't think we should silence it by putting these notifications into another email list which nobody would care about. The right thing to do would be to join hands to resolve the issues and stabilize the builds.I think keeping the CI pipeline stable should be the responsibility of the mxnet community which will enable us for quicker delivery of features and ensure there are no regressions.
the commits are already going to commits@ my 2 cents. Thanks, Naveen On Sat, Aug 26, 2017 at 4:12 PM, Nan Zhu <[email protected]> wrote: > Hi, all > > this building result is a big noise here, I think Spark has a separate mail > list for building results/commit record, etc., can we do that as well? > > and master branch has been broken for a while, looks like Python2/3: MKLML > is the deal breaker > > Best, > > Nan > > > On Thu, Aug 24, 2017 at 12:52 PM, Apache Jenkins Server < > [email protected]> wrote: > > > Build for MXNet branch master has broken. Please view the build at > > https://builds.apache.org/job/incubator-mxnet/job/master/229/ >
