We can enable building nightlys for feature branches too. 

Sam

> On Jan 10, 2020, at 7:48 PM, Lin Yuan <apefor...@gmail.com> wrote:
> 
> We can release one cpu-mkl and one CUDA wheel  for testing various
> applications. Other people can build from source if they want other flavors
> 
> Lin
> 
>> On Fri, Jan 10, 2020 at 4:00 PM Karan Jariwala <karankjariw...@gmail.com>
>> wrote:
>> 
>> Yes, agree with your point. But we will be requiring  many flavors of pip
>> wheel.
>> 
>> MKL/ without MKL
>> CUDA/ no CUDA
>> Linux/windows/Mac
>> 
>> Thanks,
>> Karan
>> 
>> On Fri, Jan 10, 2020 at 3:54 PM Haibin Lin <haibin.lin....@gmail.com>
>> wrote:
>> 
>>> Shall we provide pip wheels for later release votes?
>>> 
>>> Not everyone knows how to build MXNet from source (and building from
>> source
>>> also takes very long). Providing a pip wheel would lower the bar for
>> users
>>> who wants to test MXNet and participate in voting.
>>> 
>>> Best,
>>> Haibin
>>> 
>>> On Fri, Jan 10, 2020 at 3:50 PM Haibin Lin <haibin.lin....@gmail.com>
>>> wrote:
>>> 
>>>> +1
>>>> 
>>>> Built from source with USE_CUDA=1 on Ubuntu. Run gluon-nlp unit tests
>> and
>>>> they passed.
>>>> 
>>>> On Fri, Jan 10, 2020 at 3:18 PM Karan Jariwala <
>> karankjariw...@gmail.com
>>>> 
>>>> wrote:
>>>> 
>>>>> +1
>>>>> 
>>>>> Tested MXNet with and without MKL-DNN on Ubuntu 16.04 with Horovod
>>> 0.18.2.
>>>>> No regression seen between 1.5.1 and 1.6.0.rc1 when running
>>> horovod_MXNet
>>>>> integration test.
>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Karan
>>>>> 
>>>>> On Fri, Jan 10, 2020 at 2:47 PM Markus Weimer <wei...@apache.org>
>>> wrote:
>>>>> 
>>>>>> +1 (binding)
>>>>>> 
>>>>>> I tested on Ubuntu 18.04 on the Windows Subsystem for Linux.
>>>>>> 
>>>>>> Tested:
>>>>>>  * Built from source using the instructions here [0]
>>>>>>  * Ran the tests in `./build/tests/mxnet_unit_tests`
>>>>>>  * SHA512 of the archive
>>>>>> 
>>>>>> Not tested:
>>>>>>  * Language bindings
>>>>>>  * CUDA or other GPU acceleration
>>>>>>  * LICENSE and compliance status
>>>>>>  * Signature of the archive
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 

Reply via email to