date:20200109

RE: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

2020-01-09 Thread Chen, Ciyong

+1

Build from source on CentOS 7.6 with GCC 4.8.5 with MKLDNN.
Unit tests passed and imagenet examples (with MKL-DNN subgraph backend) looked 
good on performance and accuracy in both FP32 and INT8 mode, RNN training 
worked.

Thanks,
-Ciyong

-Original Message-
From: Lai Wei  
Sent: Wednesday, January 8, 2020 8:56 AM
To: dev@mxnet.incubator.apache.org
Cc: d...@mxnet.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

+1
Build from source on Ubuntu with CUDA/CUDNN/MKLDNN and tested with keras-mxnet.
Unit tests passed and example works on CPU/GPU.


Best Regards

Lai


On Tue, Jan 7, 2020 at 11:49 AM Lin Yuan  wrote:

> Correction: it was built from source on Ubuntu 16.04
>
> On Tue, Jan 7, 2020 at 11:42 AM Lin Yuan  wrote:
>
> > +1
> >
> > Build from source on Ubuntu 18 with CUDA/CUDNN/NCCL on and verified 
> > it works with Horovod 0.18.2
> >
> > On Tue, Jan 7, 2020 at 9:55 AM Przemysław Trędak 
> > 
> > wrote:
> >
> >> Dear MXNet community,
> >>
> >> This is the vote to release Apache MXNet (incubating) version 1.6.0.
> >> Voting starts today and will close on Friday 1/10/2020 23:59 PST.
> >>
> >> Link to release notes:
> >> https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+not
> >> es
> >>
> >> Link to release candidate:
> >> https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc1
> >>
> >> Link to source and signatures on apache dist server:
> >> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc1/
> >>
> >> The differences comparing to previous release candidate 1.6.0.rc0:
> >> * Fix for RNN gradient calculation for MKLDNN ([v1.6.x] Cherry-pick 
> >> MKL-DNN Rnn operator enhancements to v1.6.x (#17225))
> >> * Fix for Windows CMake build (Backport #16980 #17031 #17018 #17019 
> >> to
> >> 1.6 branch (#17213))
> >> * CPU counterpart to contrib multihead attention operators 
> >> (Interleaved MHA for CPU path (#17138) (#17211))
> >> * Fix for #16060 (fix norm sparse fallback (#17149))
> >> * Fix for inconsistent names in estimator API (fix parameter names 
> >> in
> the
> >> estimator api (#17051) (#17162))
> >> * Fixes for OpenMP (Backport 3rdparty/openmp fixes (#17193))
> >> * Fix for pointwise fusion speed for large networks (which was the
> reason
> >> of -1 in the vote for rc0) as well as fixes for nondeterminism in 
> >> sum of squares operator and trainer parameter order (Backport 
> >> #17002, #17068
> and
> >> #17114 to 1.6 branch (#17137))
> >>
> >>
> >> Please remember to TEST first before voting accordingly:
> >> +1 = approve
> >> +0 = no opinion
> >> -1 = disapprove (provide reason)
> >>
> >>
> >> Best regards,
> >> Przemyslaw Tredak
> >>
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

2020-01-09 Thread guanxin qiao




On 2020/01/07 17:55:15, Przemys��aw Tr��dak  wrote: 
> Dear MXNet community,
> 
> This is the vote to release Apache MXNet (incubating) version 1.6.0. Voting 
> starts today and will close on Friday 1/10/2020 23:59 PST.
> 
> Link to release notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
> 
> Link to release candidate:
> https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc1
> 
> Link to source and signatures on apache dist server:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc1/
> 
> The differences comparing to previous release candidate 1.6.0.rc0:
> * Fix for RNN gradient calculation for MKLDNN ([v1.6.x] Cherry-pick MKL-DNN 
> Rnn operator enhancements to v1.6.x (#17225))
> * Fix for Windows CMake build (Backport #16980 #17031 #17018 #17019 to 1.6 
> branch (#17213))
> * CPU counterpart to contrib multihead attention operators (Interleaved MHA 
> for CPU path (#17138) (#17211))
> * Fix for #16060 (fix norm sparse fallback (#17149))
> * Fix for inconsistent names in estimator API (fix parameter names in the 
> estimator api (#17051) (#17162))
> * Fixes for OpenMP (Backport 3rdparty/openmp fixes (#17193))
> * Fix for pointwise fusion speed for large networks (which was the reason of 
> -1 in the vote for rc0) as well as fixes for nondeterminism in sum of squares 
> operator and trainer parameter order (Backport #17002, #17068 and #17114 to 
> 1.6 branch (#17137))
> 
> 
> Please remember to TEST first before voting accordingly:
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
> 
> 
> Best regards,
> Przemyslaw Tredak
> 

+1
Built from source on Ubuntu 18 with CUDA/CUDNN. Inference worked well without 
speed/accuracy drop.

Thanks.

CCLA for MXNET

2020-01-09 Thread Gil Yehuda

Dear MXNet Dev team
I have a team at Verizon who would like to start contributing code to
MXNet. In preparation, would you need a CCLA in place between Verizon and
Apache listing their names? and ICLAs from them? if so I'll be glad to make
this happen. I didn't see the CLA indicated on the contributing
documentation in the repo, so I'm asking just in case. Thanks

Gil Yehuda: I help with external technology engagement

>From the Open Source Program Office
 at Yahoo --> Oath - ->
Verizon Media

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

2020-01-09 Thread Chen, Xinyu1

+1

Build from source on CentOS 7.6 with MKL/DNNL on and verified it works with 
DNNL backend for fp32/int8 inference.
Both functionality and performance are great 

Thanks
Xinyu

On 2020/1/8, 1:55 AM, "Przemysław Trędak"  wrote:

Dear MXNet community,

This is the vote to release Apache MXNet (incubating) version 1.6.0. Voting 
starts today and will close on Friday 1/10/2020 23:59 PST.

Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes

Link to release candidate:
https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc1

Link to source and signatures on apache dist server:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc1/

The differences comparing to previous release candidate 1.6.0.rc0:
* Fix for RNN gradient calculation for MKLDNN ([v1.6.x] Cherry-pick MKL-DNN 
Rnn operator enhancements to v1.6.x (#17225))
* Fix for Windows CMake build (Backport #16980 #17031 #17018 #17019 to 1.6 
branch (#17213))
* CPU counterpart to contrib multihead attention operators (Interleaved MHA 
for CPU path (#17138) (#17211))
* Fix for #16060 (fix norm sparse fallback (#17149))
* Fix for inconsistent names in estimator API (fix parameter names in the 
estimator api (#17051) (#17162))
* Fixes for OpenMP (Backport 3rdparty/openmp fixes (#17193))
* Fix for pointwise fusion speed for large networks (which was the reason 
of -1 in the vote for rc0) as well as fixes for nondeterminism in sum of 
squares operator and trainer parameter order (Backport #17002, #17068 and 
#17114 to 1.6 branch (#17137))


Please remember to TEST first before voting accordingly:
+1 = approve
+0 = no opinion
-1 = disapprove (provide reason)


Best regards,
Przemyslaw Tredak

Re: CD with windows need a special jenkins slave machine like restricted-utility

2020-01-09 Thread Pedro Larroy

Is there a solution for this error in VS2017?

c:\users\administrator\mxnet\src\operator\mxnet_op.h(943) : fatal error
C1002: compiler is out of heap space in pass 2



On Tue, Jan 7, 2020 at 5:11 PM shiwen hu  wrote:

> >
> > I personally encountered the problem that 2015 can't compile in high
> > version cuda. But I can't remember the details. We can continue to use
> 2015
> > until we encounter problems.
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

2020-01-09 Thread Zhi Zhang

+1 built from source and passed gluoncv unittests

Thanks,
Zhi

On 2020/01/07 17:55:15, Przemys��aw Tr��dak  wrote: 
> Dear MXNet community,
> 
> This is the vote to release Apache MXNet (incubating) version 1.6.0. Voting 
> starts today and will close on Friday 1/10/2020 23:59 PST.
> 
> Link to release notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
> 
> Link to release candidate:
> https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc1
> 
> Link to source and signatures on apache dist server:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc1/
> 
> The differences comparing to previous release candidate 1.6.0.rc0:
> * Fix for RNN gradient calculation for MKLDNN ([v1.6.x] Cherry-pick MKL-DNN 
> Rnn operator enhancements to v1.6.x (#17225))
> * Fix for Windows CMake build (Backport #16980 #17031 #17018 #17019 to 1.6 
> branch (#17213))
> * CPU counterpart to contrib multihead attention operators (Interleaved MHA 
> for CPU path (#17138) (#17211))
> * Fix for #16060 (fix norm sparse fallback (#17149))
> * Fix for inconsistent names in estimator API (fix parameter names in the 
> estimator api (#17051) (#17162))
> * Fixes for OpenMP (Backport 3rdparty/openmp fixes (#17193))
> * Fix for pointwise fusion speed for large networks (which was the reason of 
> -1 in the vote for rc0) as well as fixes for nondeterminism in sum of squares 
> operator and trainer parameter order (Backport #17002, #17068 and #17114 to 
> 1.6 branch (#17137))
> 
> 
> Please remember to TEST first before voting accordingly:
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
> 
> 
> Best regards,
> Przemyslaw Tredak
>

[apache/incubator-mxnet] [mxnet 2.0][item 4.8][RFC] Gluon Data API Extension and Fixes(Part 1) (#17263)

2020-01-09 Thread Joshua Z. Zhang

## Description

This is the part 1 of Gluon Data API extension and fixes, which mainly focus on 
cleaning up diverging usage of mxnet module/gluon.
Through long time evolution, there's currently two streams of data loading 
conventions implemented in mxnet
- Iterator: 
mxnet.io.DataIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L180)
- Dataset + DataLoader: gluon.data.Dataset + gluon.data.DataLoader

In order to eliminate the confusion here and to reduce the maintenance efforts, 
the plan is to drop all old iterators and provide similar Dataset + Dataloader 
experience in gluon data API. 
## Things to be removed

### iterators
- Base 
mxnet.io.DataIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L180)
- 
mxnet.io.ResizeIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L282)
- 
mxnet.io.PrefetchIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L347)
- 
mxnet.io.NDArrayIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L491)
- 
mxnet.io.MXDataIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/io/io.py#L800)
- 
mxnet.image.ImageIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/image/detection.py#L626)
- 
mxnet.image.ImageDetIter(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/image/detection.py#L626)

### Augmenters from mxnet.image and mxnet.image.detection module

Random augmenters, e.g. 
(https://github.com/apache/incubator-mxnet/blob/ac88f1e87aa7da2c33f0cb89524d444ddc3a2ae8/python/mxnet/image/image.py#L615)
 will be removed.

### Transform = args in gluon.data.Datasets

transform = is no longer supported, and can be replaced with 
`dataset.transform` or `dataset.transform_first`

## Things to be added

### Gluon Data Datasets

Dataset + Transfrom combo that simulate the removed Iterators

For example, NDArrayIter can be reimplemented as NDArrayDataset + empty 
transform function.

### Gluon Data Augmentaters/Transforms

Data augmenters as mxnet.gluon.Block

Candidates TBD, useful candidates from 
GluonCV(https://github.com/dmlc/gluon-cv/tree/master/gluoncv/data/transforms) 
and 
GluonNLP(https://github.com/dmlc/gluon-nlp/blob/v0.8.x/src/gluonnlp/data/transforms.py)

### mxnet.image

image processing functions will be absorbed from 
GluonCV(https://github.com/dmlc/gluon-cv/blob/master/gluoncv/data/transforms/image.py)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17263

Re: Stopping nightly releases to Pypi

2020-01-09 Thread Chris Olivier

If this tiny fix is representative of the bulk of the reasoning behind all
the the CD churn recently, then this seems to be of some concern.

-Chris

On Thu, Jan 9, 2020 at 6:32 AM Marco de Abreu 
wrote:

> Great, thanks a lot sheng!
>
> -Marco
>
> Sheng Zha  schrieb am Do., 9. Jan. 2020, 14:28:
>
> > I'm fixing the CD pipeline in
> > https://github.com/apache/incubator-mxnet/pull/17259/files and will
> > update the s3 publish path so that it's friendly for automatically
> > generating such page.
> >
> > -sz
> >
> > On 2020/01/06 18:19:52, "Lausen, Leonard" 
> > wrote:
> > > Consider a user finds a bug in a nightly version but we can't narrow
> > down the
> > > version of mxnet used as the name is constant over time. Or users wan't
> > to
> > > revert back to the previous nightly version installed but don't know
> > which date
> > > it was from due to constant name.
> > >
> > > Instead I suggest we introduce an autogenerated page like
> > > https://download.pytorch.org/whl/nightly/cu101/torch_nightly.html
> > >
> > > Then "pip install -f URLTOPAGE mxnet" will install the latest available
> > version.
> > > Maybe the team maintaining the S3 bucket can reconsider creating such
> > page for
> > > the intermediate time until the CD based nighlty build is operating.
> > >
> > > On Mon, 2020-01-06 at 10:01 -0800, Lin Yuan wrote:
> > > > +1 for a nightly pip with fixed name.
> > > >
> > > > We need this to track mxnet integration with other packages such as
> > Horovod.
> > > >
> > > > Sam, when do you think we can have this nightly build with a fixed
> > name?
> > > >
> > > > Thanks,
> > > >
> > > > Lin
> > > >
> > > > On Sun, Jan 5, 2020 at 7:48 PM Skalicky, Sam
> > 
> > > > wrote:
> > > >
> > > > > Hi Tao,
> > > > >
> > > > > We dont have this yet, but we did think about putting the latest
> > wheels in
> > > > > a specific place in the s3 bucket so they are always updated.
> > Initially we
> > > > > decided not to do this since the main MXNet CD should have been
> > fixed. But
> > > > > since its still not fixed yet, we might try and go ahead and do
> this.
> > > > >
> > > > > Sam
> > > > >
> > > > > On Jan 5, 2020, at 6:02 PM, Lv, Tao A  > > > > tao.a...@intel.com>> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > How to install the latest available build of a flavor without
> > specifying
> > > > > the build date? Something like `pip install mxnet --pre`.
> > > > >
> > > > > Thanks,
> > > > > -tao
> > > > >
> > > > > -Original Message-
> > > > > From: Skalicky, Sam  > > > > sska...@amazon.com.INVALID>>
> > > > > Sent: Monday, January 6, 2020 2:09 AM
> > > > > To: dev@mxnet.incubator.apache.org > dev@mxnet.incubator.apache.org>
> > > > > Subject: Re: Stopping nightly releases to Pypi
> > > > >
> > > > > Hi Haibin,
> > > > >
> > > > > You typed the correct URLs, the cu100 build has been failing since
> > > > > December 30th but other builds have succeeded. The wheels are being
> > > > > delivered into a public bucket that anyone with an AWS account can
> > access
> > > > > and go poke around, here’s the URL for web access:
> > > > >
> > > > >
> > > > >
> >
> https://s3.console.aws.amazon.com/s3/buckets/apache-mxnet/dist/2020-01-01/dist/?region=us-west-2=overview
> > > > >
> > > > > You will have to log into your AWS account to access it however
> > (which
> > > > > means you’ll need an AWS account).
> > > > >
> > > > > It looks like only the following flavors are available for
> > 2020-01-01:
> > > > > mxnet
> > > > > mxnet-cu92
> > > > > mxnet-cu92mkl
> > > > > mxnet-mkl
> > > > >
> > > > > Sam
> > > > >
> > > > > On Jan 4, 2020, at 9:06 PM, Haibin Lin  >  > > > > haibin.lin@gmail.com>> wrote:
> > > > >
> > > > > I was trying the nightly builds, but none of them is available:
> > > > >
> > > > > pip3 install
> > > > >
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl
> > > > > --user
> > > > > <
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl--user
> > > > > >
> > > > > pip3 install
> > > > >
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl
> > > > > --user
> > > > > <
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl--user
> > > > > >
> > > > > pip3 install
> > > > >
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl
> > > > > --user
> > > > > <
> > > > >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl--user
> > > > > >
> > > > > pip3 install
> > > > >
> > > > >
> >
>

Re: Stopping nightly releases to Pypi

2020-01-09 Thread Marco de Abreu

Great, thanks a lot sheng!

-Marco

Sheng Zha  schrieb am Do., 9. Jan. 2020, 14:28:

> I'm fixing the CD pipeline in
> https://github.com/apache/incubator-mxnet/pull/17259/files and will
> update the s3 publish path so that it's friendly for automatically
> generating such page.
>
> -sz
>
> On 2020/01/06 18:19:52, "Lausen, Leonard" 
> wrote:
> > Consider a user finds a bug in a nightly version but we can't narrow
> down the
> > version of mxnet used as the name is constant over time. Or users wan't
> to
> > revert back to the previous nightly version installed but don't know
> which date
> > it was from due to constant name.
> >
> > Instead I suggest we introduce an autogenerated page like
> > https://download.pytorch.org/whl/nightly/cu101/torch_nightly.html
> >
> > Then "pip install -f URLTOPAGE mxnet" will install the latest available
> version.
> > Maybe the team maintaining the S3 bucket can reconsider creating such
> page for
> > the intermediate time until the CD based nighlty build is operating.
> >
> > On Mon, 2020-01-06 at 10:01 -0800, Lin Yuan wrote:
> > > +1 for a nightly pip with fixed name.
> > >
> > > We need this to track mxnet integration with other packages such as
> Horovod.
> > >
> > > Sam, when do you think we can have this nightly build with a fixed
> name?
> > >
> > > Thanks,
> > >
> > > Lin
> > >
> > > On Sun, Jan 5, 2020 at 7:48 PM Skalicky, Sam
> 
> > > wrote:
> > >
> > > > Hi Tao,
> > > >
> > > > We dont have this yet, but we did think about putting the latest
> wheels in
> > > > a specific place in the s3 bucket so they are always updated.
> Initially we
> > > > decided not to do this since the main MXNet CD should have been
> fixed. But
> > > > since its still not fixed yet, we might try and go ahead and do this.
> > > >
> > > > Sam
> > > >
> > > > On Jan 5, 2020, at 6:02 PM, Lv, Tao A  > > > tao.a...@intel.com>> wrote:
> > > >
> > > > Hi,
> > > >
> > > > How to install the latest available build of a flavor without
> specifying
> > > > the build date? Something like `pip install mxnet --pre`.
> > > >
> > > > Thanks,
> > > > -tao
> > > >
> > > > -Original Message-
> > > > From: Skalicky, Sam  > > > sska...@amazon.com.INVALID>>
> > > > Sent: Monday, January 6, 2020 2:09 AM
> > > > To: dev@mxnet.incubator.apache.org dev@mxnet.incubator.apache.org>
> > > > Subject: Re: Stopping nightly releases to Pypi
> > > >
> > > > Hi Haibin,
> > > >
> > > > You typed the correct URLs, the cu100 build has been failing since
> > > > December 30th but other builds have succeeded. The wheels are being
> > > > delivered into a public bucket that anyone with an AWS account can
> access
> > > > and go poke around, here’s the URL for web access:
> > > >
> > > >
> > > >
> https://s3.console.aws.amazon.com/s3/buckets/apache-mxnet/dist/2020-01-01/dist/?region=us-west-2=overview
> > > >
> > > > You will have to log into your AWS account to access it however
> (which
> > > > means you’ll need an AWS account).
> > > >
> > > > It looks like only the following flavors are available for
> 2020-01-01:
> > > > mxnet
> > > > mxnet-cu92
> > > > mxnet-cu92mkl
> > > > mxnet-mkl
> > > >
> > > > Sam
> > > >
> > > > On Jan 4, 2020, at 9:06 PM, Haibin Lin   > > > haibin.lin@gmail.com>> wrote:
> > > >
> > > > I was trying the nightly builds, but none of them is available:
> > > >
> > > > pip3 install
> > > >
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl
> > > > --user
> > > > <
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl--user
> > > > >
> > > > pip3 install
> > > >
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl
> > > > --user
> > > > <
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl--user
> > > > >
> > > > pip3 install
> > > >
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl
> > > > --user
> > > > <
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl--user
> > > > >
> > > > pip3 install
> > > >
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-04/dist/mxnet_cu100-1.6.0b20200104-py2.py3-none-manylinux1_x86_64.whl
> > > > --user
> > > > <
> > > >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-04/dist/mxnet_cu100-1.6.0b20200104-py2.py3-none-manylinux1_x86_64.whl--user
> > > > >
> > > >
> > > > ERROR: Could not install requirement mxnet-cu100==1.6.0b20200103 from
> > > >
>

Re: Stopping nightly releases to Pypi

2020-01-09 Thread Sheng Zha

I'm fixing the CD pipeline in 
https://github.com/apache/incubator-mxnet/pull/17259/files and will update the 
s3 publish path so that it's friendly for automatically generating such page.

-sz

On 2020/01/06 18:19:52, "Lausen, Leonard"  wrote: 
> Consider a user finds a bug in a nightly version but we can't narrow down the
> version of mxnet used as the name is constant over time. Or users wan't to
> revert back to the previous nightly version installed but don't know which 
> date
> it was from due to constant name.
> 
> Instead I suggest we introduce an autogenerated page like 
> https://download.pytorch.org/whl/nightly/cu101/torch_nightly.html
> 
> Then "pip install -f URLTOPAGE mxnet" will install the latest available 
> version.
> Maybe the team maintaining the S3 bucket can reconsider creating such page for
> the intermediate time until the CD based nighlty build is operating.
> 
> On Mon, 2020-01-06 at 10:01 -0800, Lin Yuan wrote:
> > +1 for a nightly pip with fixed name.
> > 
> > We need this to track mxnet integration with other packages such as Horovod.
> > 
> > Sam, when do you think we can have this nightly build with a fixed name?
> > 
> > Thanks,
> > 
> > Lin
> > 
> > On Sun, Jan 5, 2020 at 7:48 PM Skalicky, Sam 
> > wrote:
> > 
> > > Hi Tao,
> > > 
> > > We dont have this yet, but we did think about putting the latest wheels in
> > > a specific place in the s3 bucket so they are always updated. Initially we
> > > decided not to do this since the main MXNet CD should have been fixed. But
> > > since its still not fixed yet, we might try and go ahead and do this.
> > > 
> > > Sam
> > > 
> > > On Jan 5, 2020, at 6:02 PM, Lv, Tao A  > > tao.a...@intel.com>> wrote:
> > > 
> > > Hi,
> > > 
> > > How to install the latest available build of a flavor without specifying
> > > the build date? Something like `pip install mxnet --pre`.
> > > 
> > > Thanks,
> > > -tao
> > > 
> > > -Original Message-
> > > From: Skalicky, Sam  > > sska...@amazon.com.INVALID>>
> > > Sent: Monday, January 6, 2020 2:09 AM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: Stopping nightly releases to Pypi
> > > 
> > > Hi Haibin,
> > > 
> > > You typed the correct URLs, the cu100 build has been failing since
> > > December 30th but other builds have succeeded. The wheels are being
> > > delivered into a public bucket that anyone with an AWS account can access
> > > and go poke around, here’s the URL for web access:
> > > 
> > > 
> > > https://s3.console.aws.amazon.com/s3/buckets/apache-mxnet/dist/2020-01-01/dist/?region=us-west-2=overview
> > > 
> > > You will have to log into your AWS account to access it however (which
> > > means you’ll need an AWS account).
> > > 
> > > It looks like only the following flavors are available for 2020-01-01:
> > > mxnet
> > > mxnet-cu92
> > > mxnet-cu92mkl
> > > mxnet-mkl
> > > 
> > > Sam
> > > 
> > > On Jan 4, 2020, at 9:06 PM, Haibin Lin  > > haibin.lin@gmail.com>> wrote:
> > > 
> > > I was trying the nightly builds, but none of them is available:
> > > 
> > > pip3 install
> > > 
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl
> > > --user
> > > <
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-01/dist/mxnet_cu100-1.6.0b20200101-py2.py3-none-manylinux1_x86_64.whl--user
> > > >
> > > pip3 install
> > > 
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl
> > > --user
> > > <
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-02/dist/mxnet_cu100-1.6.0b20200102-py2.py3-none-manylinux1_x86_64.whl--user
> > > >
> > > pip3 install
> > > 
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl
> > > --user
> > > <
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl--user
> > > >
> > > pip3 install
> > > 
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-04/dist/mxnet_cu100-1.6.0b20200104-py2.py3-none-manylinux1_x86_64.whl
> > > --user
> > > <
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-04/dist/mxnet_cu100-1.6.0b20200104-py2.py3-none-manylinux1_x86_64.whl--user
> > > >
> > > 
> > > ERROR: Could not install requirement mxnet-cu100==1.6.0b20200103 from
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl
> > > because of HTTP error 404 Client Error: Not Found for url:
> > > 
> > > https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2020-01-03/dist/mxnet_cu100-1.6.0b20200103-py2.py3-none-manylinux1_x86_64.whl
> > > for URL
> > > 
> > >

RE: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

CCLA for MXNET

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

Re: CD with windows need a special jenkins slave machine like restricted-utility

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc1

[apache/incubator-mxnet] [mxnet 2.0][item 4.8][RFC] Gluon Data API Extension and Fixes(Part 1) (#17263)

Re: Stopping nightly releases to Pypi

Re: Stopping nightly releases to Pypi

Re: Stopping nightly releases to Pypi

10 matches

Site Navigation

Mail list logo

Footer information