nks!
> -Ciyong
>
> -Original Message-
> From: Zhao, Patric
> Sent: Monday, November 18, 2019 2:10 PM
> To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> Subject: RE: RE: MXNet 1.6.0 release
>
> Plan to cherry-pick below PR into 1.6. Please take a
PM
To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
Subject: RE: RE: MXNet 1.6.0 release
Plan to cherry-pick below PR into 1.6. Please take a review.
https://github.com/apache/incubator-mxnet/pull/16837
> -Original Message-
> From: Tan, Jonathan
> Sent: Monday, November 18
Plan to cherry-pick below PR into 1.6. Please take a review.
https://github.com/apache/incubator-mxnet/pull/16837
> -Original Message-
> From: Tan, Jonathan
> Sent: Monday, November 18, 2019 9:43 AM
> To: d...@mxnet.apache.org
> Subject: Re: RE: MXNet 1.6.0 releas
Hi MXNet Community,
I’ve been doing some testing on the performance of MXnet 1.6.x vs 1.5.1 and I
noticed some regression in training. You can find more details here:
https://github.com/apache/incubator-mxnet/issues/16845
Thanks,
Jonathan
On 2019/11/14 02:41:26, "Zhao, Patric" mailto:p...@intel
tric
> > Sent: Friday, November 1, 2019 12:13 PM
> > To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> > Subject: RE: RE: MXNet 1.6.0 release
> >
> > Sure, I will see the issue.
> >
> > > -Original Message-
> > > From: Przemysł
t.apache.org
> Subject: RE: RE: MXNet 1.6.0 release
>
> Sure, I will see the issue.
>
> > -Original Message-
> > From: Przemysław Trędak
> > Sent: Friday, November 1, 2019 11:27 AM
> > To: d...@mxnet.apache.org
> > Subject: Re: RE: MXNet 1.6.0 release
Sure, I will see the issue.
> -Original Message-
> From: Przemysław Trędak
> Sent: Friday, November 1, 2019 11:27 AM
> To: d...@mxnet.apache.org
> Subject: Re: RE: MXNet 1.6.0 release
>
> Hi Patric,
>
> Actually the nightly tests show some problems with m
Hi Patric,
Actually the nightly tests show some problems with machines not being able to
find libmkldnn.so.1 (see e.g. here:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/NightlyTestsForBinaries/detail/master/492/pipeline).
I'm not sure if this is just a problem with configur