Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
+1 Build from source on Mac and Ubuntu 16.04. 1. Run GAN, DCGAN using Gluon on 1 GPU in Ubuntu and CPU Mac. 2. Convert a model to fp16, save and load in Gluon, perform inference. Best, Sandeep On Fri, Nov 16, 2018, 7:01 PM Indhu +1. > > Builds fine from source. Tested few CNN examples using Python binding. > Everything looks fine. > > Thanks, > Indu > > > On Fri, Nov 16, 2018, 4:16 PM Roshani Nagmote wrote: > > > +1 > > Installed the release package on Ubuntu with CUDA, CUDNN enabled and ran > > train_cifar10.py example successfully. > > > > Thanks, > > Roshani > > > > On Fri, Nov 16, 2018 at 5:21 AM Anton Chernov > wrote: > > > > > Thank you Carin, Steffen and Kellen for your votes. > > > > > > The results so far: > > > > > > * Binding * > > > > > > +1 votes: > > > - Carin > > > > > > * Non-Binding * > > > > > > +1 votes: > > > - Kellen > > > - Steffen > > > > > > So far, we've got only positive votes, but unfortunately not enough to > > > conclude a result from the vote. I would like to remind everyone that > we > > > need at least 3 binding +1 votes. Therefore, the vote is extended until > > > Tuesday 20th of November 2018, 5pm CET (9am PT). > > > > > > I kindly ask the community to participate in voting for this patch > > release. > > > > > > Best regards > > > Anton > > > > > > > > > пт, 16 нояб. 2018 г. в 9:10, kellen sunderland < > > > kellen.sunderl...@gmail.com > > > >: > > > > > > > Just tested with 1.3.0 and those tests were failing for that release > as > > > > well. Given it's not a regression I'm +1 (non-binding). > > > > > > > > On Thu, Nov 15, 2018 at 11:52 PM kellen sunderland < > > > > kellen.sunderl...@gmail.com> wrote: > > > > > > > > > Thanks for organizing the release Anton and for testing Carin and > > > > > Steffen. Lots of great fixes in this release. As we don't have > the > > > > > required 3 committers I'd suggest extending the vote for a few > days. > > > > > > > > > > I tested the following on MacOS 10.13, High Sierra: > > > > > > > > > > INCUBATING IN RELEASE FILE: check. > > > > > LICENSE check. > > > > > NOTICE check. > > > > > SIGNATURE check. > > > > > HASH check. > > > > > DISCLAIMER check. > > > > > SOURCE COMPILES VIA MAKEFILE check. > > > > > SOURCE COMPILES VIA CMAKE check. > > > > > C++ TESTS PASS fail > > > > > Two tests failing for me. > > > > > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > > > > > -DUSE_OPENCV=0 .. > > > > > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > > > > > --gtest_filter=-GpuTopology.* > > > > > Result: > > > > > [ FAILED ] 2 tests, listed below: > > > > > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > > > > > [ FAILED ] ACTIVATION_PERF.TimingCPU > > > > > > > > > > PYHTON UNIT TESTS PASS check. > > > > > > > > > > Not sure if the test failures are a regression so I'm +0 > > (non-binding) > > > > > > > > > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel < > > > steffenroc...@gmail.com> > > > > > wrote: > > > > > > > > > >> +1 build on MacOS Sierra following instructions on > > > > >> > > > > >> > > > > > > > > > > https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac > > > > >> and run one training test. > > > > >> > > > > >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier > > > > > wrote: > > > > >> > > > > >> > +1 - Clojure package tested fine with Scala jars > > > > >> > > > > > >> > On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov < > > mecher...@gmail.com> > > > > >> wrote: > > > > >> > > > > > >> > > Dear MXNet community, > > > > >> > > > > > > >> > > This is the vote to release Apache MXNet (incubating) version > > > 1.3.1. > > > > >> > Voting > > > > >> > > will start now, on Monday the 12th of November 2018 and close > on > > > > 14:00 > > > > >> > > Thursday the 15th of November 2018, Pacific Time (PT). > > > > >> > > > > > > >> > > Link to release notes: > > > > >> > > https://cwiki.apache.org/confluence/x/eZGzBQ > > > > >> > > > > > > >> > > Link to release candidate 1.3.1.rc0: > > > > >> > > > > https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 > > > > >> > > > > > > >> > > Link to source and signatures on apache dist server: > > > > >> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ > > > > >> > > > > > > >> > > Link to scala packages on the staging repo: > > > > >> > > > > > > >> > > * CPU > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ > > > > >> > > > > > > >> > > * GPU > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ > > > > >> > > > > > > >> > > Please remember to TEST first before voting accordingly: > > > > >> > > +1 = approve > > > > >> > > +0 = no opinion > > > > >> > > -1 = disapprove (provide reason) >
Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
+1. Builds fine from source. Tested few CNN examples using Python binding. Everything looks fine. Thanks, Indu On Fri, Nov 16, 2018, 4:16 PM Roshani Nagmote +1 > Installed the release package on Ubuntu with CUDA, CUDNN enabled and ran > train_cifar10.py example successfully. > > Thanks, > Roshani > > On Fri, Nov 16, 2018 at 5:21 AM Anton Chernov wrote: > > > Thank you Carin, Steffen and Kellen for your votes. > > > > The results so far: > > > > * Binding * > > > > +1 votes: > > - Carin > > > > * Non-Binding * > > > > +1 votes: > > - Kellen > > - Steffen > > > > So far, we've got only positive votes, but unfortunately not enough to > > conclude a result from the vote. I would like to remind everyone that we > > need at least 3 binding +1 votes. Therefore, the vote is extended until > > Tuesday 20th of November 2018, 5pm CET (9am PT). > > > > I kindly ask the community to participate in voting for this patch > release. > > > > Best regards > > Anton > > > > > > пт, 16 нояб. 2018 г. в 9:10, kellen sunderland < > > kellen.sunderl...@gmail.com > > >: > > > > > Just tested with 1.3.0 and those tests were failing for that release as > > > well. Given it's not a regression I'm +1 (non-binding). > > > > > > On Thu, Nov 15, 2018 at 11:52 PM kellen sunderland < > > > kellen.sunderl...@gmail.com> wrote: > > > > > > > Thanks for organizing the release Anton and for testing Carin and > > > > Steffen. Lots of great fixes in this release. As we don't have the > > > > required 3 committers I'd suggest extending the vote for a few days. > > > > > > > > I tested the following on MacOS 10.13, High Sierra: > > > > > > > > INCUBATING IN RELEASE FILE: check. > > > > LICENSE check. > > > > NOTICE check. > > > > SIGNATURE check. > > > > HASH check. > > > > DISCLAIMER check. > > > > SOURCE COMPILES VIA MAKEFILE check. > > > > SOURCE COMPILES VIA CMAKE check. > > > > C++ TESTS PASS fail > > > > Two tests failing for me. > > > > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > > > > -DUSE_OPENCV=0 .. > > > > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > > > > --gtest_filter=-GpuTopology.* > > > > Result: > > > > [ FAILED ] 2 tests, listed below: > > > > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > > > > [ FAILED ] ACTIVATION_PERF.TimingCPU > > > > > > > > PYHTON UNIT TESTS PASS check. > > > > > > > > Not sure if the test failures are a regression so I'm +0 > (non-binding) > > > > > > > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel < > > steffenroc...@gmail.com> > > > > wrote: > > > > > > > >> +1 build on MacOS Sierra following instructions on > > > >> > > > >> > > > > > > https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac > > > >> and run one training test. > > > >> > > > >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier > > > wrote: > > > >> > > > >> > +1 - Clojure package tested fine with Scala jars > > > >> > > > > >> > On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov < > mecher...@gmail.com> > > > >> wrote: > > > >> > > > > >> > > Dear MXNet community, > > > >> > > > > > >> > > This is the vote to release Apache MXNet (incubating) version > > 1.3.1. > > > >> > Voting > > > >> > > will start now, on Monday the 12th of November 2018 and close on > > > 14:00 > > > >> > > Thursday the 15th of November 2018, Pacific Time (PT). > > > >> > > > > > >> > > Link to release notes: > > > >> > > https://cwiki.apache.org/confluence/x/eZGzBQ > > > >> > > > > > >> > > Link to release candidate 1.3.1.rc0: > > > >> > > > https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 > > > >> > > > > > >> > > Link to source and signatures on apache dist server: > > > >> > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ > > > >> > > > > > >> > > Link to scala packages on the staging repo: > > > >> > > > > > >> > > * CPU > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ > > > >> > > > > > >> > > * GPU > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ > > > >> > > > > > >> > > Please remember to TEST first before voting accordingly: > > > >> > > +1 = approve > > > >> > > +0 = no opinion > > > >> > > -1 = disapprove (provide reason) > > > >> > > > > > >> > > > > > >> > > Best regards, > > > >> > > Anton > > > >> > > > > > >> > > > > >> > > > > > > > > > >
Merging java-api Branch
Hi All, Just wanted to let you know that the work for MXNet Java-API was done on the 'java-api' branch and contributed by multiple contributors, I merged the PR[1] and later realized that the squash/merge credited all code contribution to one contributor. we are going to revert the commit and merge directly from the java-api branch to master like we did for the Julia PR. The code has been already code-reviewed[1] [1] https://github.com/apache/incubator-mxnet/pull/13162 Thanks, Naveen
Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
+1 Installed the release package on Ubuntu with CUDA, CUDNN enabled and ran train_cifar10.py example successfully. Thanks, Roshani On Fri, Nov 16, 2018 at 5:21 AM Anton Chernov wrote: > Thank you Carin, Steffen and Kellen for your votes. > > The results so far: > > * Binding * > > +1 votes: > - Carin > > * Non-Binding * > > +1 votes: > - Kellen > - Steffen > > So far, we've got only positive votes, but unfortunately not enough to > conclude a result from the vote. I would like to remind everyone that we > need at least 3 binding +1 votes. Therefore, the vote is extended until > Tuesday 20th of November 2018, 5pm CET (9am PT). > > I kindly ask the community to participate in voting for this patch release. > > Best regards > Anton > > > пт, 16 нояб. 2018 г. в 9:10, kellen sunderland < > kellen.sunderl...@gmail.com > >: > > > Just tested with 1.3.0 and those tests were failing for that release as > > well. Given it's not a regression I'm +1 (non-binding). > > > > On Thu, Nov 15, 2018 at 11:52 PM kellen sunderland < > > kellen.sunderl...@gmail.com> wrote: > > > > > Thanks for organizing the release Anton and for testing Carin and > > > Steffen. Lots of great fixes in this release. As we don't have the > > > required 3 committers I'd suggest extending the vote for a few days. > > > > > > I tested the following on MacOS 10.13, High Sierra: > > > > > > INCUBATING IN RELEASE FILE: check. > > > LICENSE check. > > > NOTICE check. > > > SIGNATURE check. > > > HASH check. > > > DISCLAIMER check. > > > SOURCE COMPILES VIA MAKEFILE check. > > > SOURCE COMPILES VIA CMAKE check. > > > C++ TESTS PASS fail > > > Two tests failing for me. > > > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > > > -DUSE_OPENCV=0 .. > > > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > > > --gtest_filter=-GpuTopology.* > > > Result: > > > [ FAILED ] 2 tests, listed below: > > > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > > > [ FAILED ] ACTIVATION_PERF.TimingCPU > > > > > > PYHTON UNIT TESTS PASS check. > > > > > > Not sure if the test failures are a regression so I'm +0 (non-binding) > > > > > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel < > steffenroc...@gmail.com> > > > wrote: > > > > > >> +1 build on MacOS Sierra following instructions on > > >> > > >> > > > https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac > > >> and run one training test. > > >> > > >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier > > wrote: > > >> > > >> > +1 - Clojure package tested fine with Scala jars > > >> > > > >> > On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov > > >> wrote: > > >> > > > >> > > Dear MXNet community, > > >> > > > > >> > > This is the vote to release Apache MXNet (incubating) version > 1.3.1. > > >> > Voting > > >> > > will start now, on Monday the 12th of November 2018 and close on > > 14:00 > > >> > > Thursday the 15th of November 2018, Pacific Time (PT). > > >> > > > > >> > > Link to release notes: > > >> > > https://cwiki.apache.org/confluence/x/eZGzBQ > > >> > > > > >> > > Link to release candidate 1.3.1.rc0: > > >> > > https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 > > >> > > > > >> > > Link to source and signatures on apache dist server: > > >> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ > > >> > > > > >> > > Link to scala packages on the staging repo: > > >> > > > > >> > > * CPU > > >> > > > > >> > > > > >> > > > >> > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ > > >> > > > > >> > > * GPU > > >> > > > > >> > > > > >> > > > >> > > > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ > > >> > > > > >> > > Please remember to TEST first before voting accordingly: > > >> > > +1 = approve > > >> > > +0 = no opinion > > >> > > -1 = disapprove (provide reason) > > >> > > > > >> > > > > >> > > Best regards, > > >> > > Anton > > >> > > > > >> > > > >> > > > > > >
Re: LabelBot New Design in Production
I believe having this label - [suggest-closed] is helpful. 1. Adding this label is not an automated bot script that marks stale issues. A bot script would definitely be unwelcoming and also miss major issues just because it is stale. 2. This label is simply a way to identify issues that can be closed. There are many community members who submits PRs/suggest steps for the fix but cannot actually close the issue when deemed appropriate. Right now, a committer is tagged on the issue to be closed. With this label, any committer can see issues with this label and take appropriate action. 3. From what I see, community members are going through the issues, submitting the fix, responding with solutions or questions, waiting for confirmation and finally, label the issue. So I do not see why this is unwelcoming. 4. This label is not just for stale issues. This is simply a label to allow more committers to easily keep issues folder tidy in collaboration with community members. Best, Sandeep On Fri, Nov 16, 2018 at 11:52 AM Sheng Zha wrote: > Thanks, Harsh. I saw that this was created and used on several issues and I > removed it for now because: > > - the issues that they are used on issues that don't seem to be resolved. > > - it leaves the impression to the requesters that people think their issues > are not worth people's attention in this community, which seems > unwelcoming. > > - it seems to be equivalent to issues "some existing label" + "for a long > time", which means it doesn't add value to classifying the issues. > > > If the goal is to identify stale issues, how about create an issue or a > wiki page, and have a script to update the stale issue list periodically? > This way, committers can always go visit that issue/wikipage and help with > the stale issues. It also forms the basis for a public dashboard for other > aspects of the project, which is likely worthwhile. > > > What do you think? > > > > Best regards, > > -sz > > On Fri, Nov 16, 2018 at 11:41 AM Harsh Patel > wrote: > > > Hey all, > > To help with how we handle issues for MXNet, I am proposing a new label > be > > created called: [suggest-closed]. I, alongside many others, observe many > > stale issues which can be candidates for closure and searching for these > of > > the 800+ issues we have is a daunting task. This label is meant to help > tag > > issues which the community believes should be closed. To clarify, this is > > not meant to actually close issues, it is simply a suggestion which > > contributors can feel free to label. If I am able to get a committer to > > help create this that would be great! > > > > Best, > > -Harsh > > > > On Thu, Nov 8, 2018 at 11:28 PM Hagay Lupesko wrote: > > > > > > > > > improve over time (think about it recommending you to check out the > > > discuss > > > > forum when you ask a question, asking you to provide a minimum > > > reproducible > > > > example if you report a bug, etc). That way, we would reduce the > amount > > > > boilerplate in the issue template and at the same time provide the > user > > > > with custom tailored assistance. > > > > > > > > Best regards, > > > > Marco > > > > > > > > On Fri, Nov 9, 2018 at 1:00 AM Naveen Swamy > > wrote: > > > > > > > > > Great job!, this is very helpful to triage issues!, users when > > > creating a > > > > > new Issue could themselves tag the issues. May be we should add > that > > to > > > > the > > > > > issue template? > > > > > > > > > > On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel < > > harshpatel081...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hey all, > > > > > > The upgraded label bot has been pushed into production. Current > > > > > > functionality includes > > > > > > add, delete, and update. > > > > > > (i.e. @mxnet-label-bot add ['label'] > > > > > > @mxnet-label-bot remove ['label'] > > > > > > @mxnet-label-bot update ['label']) > > > > > > > > > > > > Users should feel free to leave suggestions and any potential > > issues. > > > > The > > > > > > forum to this best would be here: > > > > > > https://github.com/apache/incubator-mxnet/issues/13163 > > > > > > > > > > > > Best, > > > > > > -Harsh Patel > > > > > > > > > > > > > > > > > > > > > -- Sandeep Krishnamurthy
Re: LabelBot New Design in Production
Thanks, Harsh. I saw that this was created and used on several issues and I removed it for now because: - the issues that they are used on issues that don't seem to be resolved. - it leaves the impression to the requesters that people think their issues are not worth people's attention in this community, which seems unwelcoming. - it seems to be equivalent to issues "some existing label" + "for a long time", which means it doesn't add value to classifying the issues. If the goal is to identify stale issues, how about create an issue or a wiki page, and have a script to update the stale issue list periodically? This way, committers can always go visit that issue/wikipage and help with the stale issues. It also forms the basis for a public dashboard for other aspects of the project, which is likely worthwhile. What do you think? Best regards, -sz On Fri, Nov 16, 2018 at 11:41 AM Harsh Patel wrote: > Hey all, > To help with how we handle issues for MXNet, I am proposing a new label be > created called: [suggest-closed]. I, alongside many others, observe many > stale issues which can be candidates for closure and searching for these of > the 800+ issues we have is a daunting task. This label is meant to help tag > issues which the community believes should be closed. To clarify, this is > not meant to actually close issues, it is simply a suggestion which > contributors can feel free to label. If I am able to get a committer to > help create this that would be great! > > Best, > -Harsh > > On Thu, Nov 8, 2018 at 11:28 PM Hagay Lupesko wrote: > > > > > > improve over time (think about it recommending you to check out the > > discuss > > > forum when you ask a question, asking you to provide a minimum > > reproducible > > > example if you report a bug, etc). That way, we would reduce the amount > > > boilerplate in the issue template and at the same time provide the user > > > with custom tailored assistance. > > > > > > Best regards, > > > Marco > > > > > > On Fri, Nov 9, 2018 at 1:00 AM Naveen Swamy > wrote: > > > > > > > Great job!, this is very helpful to triage issues!, users when > > creating a > > > > new Issue could themselves tag the issues. May be we should add that > to > > > the > > > > issue template? > > > > > > > > On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel < > harshpatel081...@gmail.com > > > > > > > wrote: > > > > > > > > > Hey all, > > > > > The upgraded label bot has been pushed into production. Current > > > > > functionality includes > > > > > add, delete, and update. > > > > > (i.e. @mxnet-label-bot add ['label'] > > > > > @mxnet-label-bot remove ['label'] > > > > > @mxnet-label-bot update ['label']) > > > > > > > > > > Users should feel free to leave suggestions and any potential > issues. > > > The > > > > > forum to this best would be here: > > > > > https://github.com/apache/incubator-mxnet/issues/13163 > > > > > > > > > > Best, > > > > > -Harsh Patel > > > > > > > > > > > > > > >
Re: LabelBot New Design in Production
Hey all, To help with how we handle issues for MXNet, I am proposing a new label be created called: [suggest-closed]. I, alongside many others, observe many stale issues which can be candidates for closure and searching for these of the 800+ issues we have is a daunting task. This label is meant to help tag issues which the community believes should be closed. To clarify, this is not meant to actually close issues, it is simply a suggestion which contributors can feel free to label. If I am able to get a committer to help create this that would be great! Best, -Harsh On Thu, Nov 8, 2018 at 11:28 PM Hagay Lupesko wrote: > > > improve over time (think about it recommending you to check out the > discuss > > forum when you ask a question, asking you to provide a minimum > reproducible > > example if you report a bug, etc). That way, we would reduce the amount > > boilerplate in the issue template and at the same time provide the user > > with custom tailored assistance. > > > > Best regards, > > Marco > > > > On Fri, Nov 9, 2018 at 1:00 AM Naveen Swamy wrote: > > > > > Great job!, this is very helpful to triage issues!, users when > creating a > > > new Issue could themselves tag the issues. May be we should add that to > > the > > > issue template? > > > > > > On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel > > > > wrote: > > > > > > > Hey all, > > > > The upgraded label bot has been pushed into production. Current > > > > functionality includes > > > > add, delete, and update. > > > > (i.e. @mxnet-label-bot add ['label'] > > > > @mxnet-label-bot remove ['label'] > > > > @mxnet-label-bot update ['label']) > > > > > > > > Users should feel free to leave suggestions and any potential issues. > > The > > > > forum to this best would be here: > > > > https://github.com/apache/incubator-mxnet/issues/13163 > > > > > > > > Best, > > > > -Harsh Patel > > > > > > > > > >
Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
Thank you Carin, Steffen and Kellen for your votes. The results so far: * Binding * +1 votes: - Carin * Non-Binding * +1 votes: - Kellen - Steffen So far, we've got only positive votes, but unfortunately not enough to conclude a result from the vote. I would like to remind everyone that we need at least 3 binding +1 votes. Therefore, the vote is extended until Tuesday 20th of November 2018, 5pm CET (9am PT). I kindly ask the community to participate in voting for this patch release. Best regards Anton пт, 16 нояб. 2018 г. в 9:10, kellen sunderland : > Just tested with 1.3.0 and those tests were failing for that release as > well. Given it's not a regression I'm +1 (non-binding). > > On Thu, Nov 15, 2018 at 11:52 PM kellen sunderland < > kellen.sunderl...@gmail.com> wrote: > > > Thanks for organizing the release Anton and for testing Carin and > > Steffen. Lots of great fixes in this release. As we don't have the > > required 3 committers I'd suggest extending the vote for a few days. > > > > I tested the following on MacOS 10.13, High Sierra: > > > > INCUBATING IN RELEASE FILE: check. > > LICENSE check. > > NOTICE check. > > SIGNATURE check. > > HASH check. > > DISCLAIMER check. > > SOURCE COMPILES VIA MAKEFILE check. > > SOURCE COMPILES VIA CMAKE check. > > C++ TESTS PASS fail > > Two tests failing for me. > > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > > -DUSE_OPENCV=0 .. > > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > > --gtest_filter=-GpuTopology.* > > Result: > > [ FAILED ] 2 tests, listed below: > > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > > [ FAILED ] ACTIVATION_PERF.TimingCPU > > > > PYHTON UNIT TESTS PASS check. > > > > Not sure if the test failures are a regression so I'm +0 (non-binding) > > > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel > > wrote: > > > >> +1 build on MacOS Sierra following instructions on > >> > >> > https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac > >> and run one training test. > >> > >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier > wrote: > >> > >> > +1 - Clojure package tested fine with Scala jars > >> > > >> > On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov > >> wrote: > >> > > >> > > Dear MXNet community, > >> > > > >> > > This is the vote to release Apache MXNet (incubating) version 1.3.1. > >> > Voting > >> > > will start now, on Monday the 12th of November 2018 and close on > 14:00 > >> > > Thursday the 15th of November 2018, Pacific Time (PT). > >> > > > >> > > Link to release notes: > >> > > https://cwiki.apache.org/confluence/x/eZGzBQ > >> > > > >> > > Link to release candidate 1.3.1.rc0: > >> > > https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 > >> > > > >> > > Link to source and signatures on apache dist server: > >> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ > >> > > > >> > > Link to scala packages on the staging repo: > >> > > > >> > > * CPU > >> > > > >> > > > >> > > >> > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ > >> > > > >> > > * GPU > >> > > > >> > > > >> > > >> > https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ > >> > > > >> > > Please remember to TEST first before voting accordingly: > >> > > +1 = approve > >> > > +0 = no opinion > >> > > -1 = disapprove (provide reason) > >> > > > >> > > > >> > > Best regards, > >> > > Anton > >> > > > >> > > >> > > >
Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0
Just tested with 1.3.0 and those tests were failing for that release as well. Given it's not a regression I'm +1 (non-binding). On Thu, Nov 15, 2018 at 11:52 PM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Thanks for organizing the release Anton and for testing Carin and > Steffen. Lots of great fixes in this release. As we don't have the > required 3 committers I'd suggest extending the vote for a few days. > > I tested the following on MacOS 10.13, High Sierra: > > INCUBATING IN RELEASE FILE: check. > LICENSE check. > NOTICE check. > SIGNATURE check. > HASH check. > DISCLAIMER check. > SOURCE COMPILES VIA MAKEFILE check. > SOURCE COMPILES VIA CMAKE check. > C++ TESTS PASS fail > Two tests failing for me. > Build with flags: cmake -DUSE_CUDA=0 -DUSE_CUDNN=0 -DUSE_OPENMP=0 > -DUSE_OPENCV=0 .. > Ran c++ tests with exclusions: ./tests/mxnet_unit_tests > --gtest_filter=-GpuTopology.* > Result: > [ FAILED ] 2 tests, listed below: > [ FAILED ] ACTIVATION_PERF.ExecuteBidirectional > [ FAILED ] ACTIVATION_PERF.TimingCPU > > PYHTON UNIT TESTS PASS check. > > Not sure if the test failures are a regression so I'm +0 (non-binding) > > On Thu, Nov 15, 2018 at 5:43 PM Steffen Rochel > wrote: > >> +1 build on MacOS Sierra following instructions on >> >> https://cwiki.apache.org/confluence/display/MXNET/MXNet+Developer+Setup+on+Mac >> and run one training test. >> >> On Tue, Nov 13, 2018 at 2:34 PM Carin Meier wrote: >> >> > +1 - Clojure package tested fine with Scala jars >> > >> > On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov >> wrote: >> > >> > > Dear MXNet community, >> > > >> > > This is the vote to release Apache MXNet (incubating) version 1.3.1. >> > Voting >> > > will start now, on Monday the 12th of November 2018 and close on 14:00 >> > > Thursday the 15th of November 2018, Pacific Time (PT). >> > > >> > > Link to release notes: >> > > https://cwiki.apache.org/confluence/x/eZGzBQ >> > > >> > > Link to release candidate 1.3.1.rc0: >> > > https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0 >> > > >> > > Link to source and signatures on apache dist server: >> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/ >> > > >> > > Link to scala packages on the staging repo: >> > > >> > > * CPU >> > > >> > > >> > >> https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-osx-x86_64-cpu/1.3.1-SNAPSHOT/ >> > > >> > > * GPU >> > > >> > > >> > >> https://repository.apache.org/content/repositories/snapshots/org/apache/mxnet/mxnet-full_2.11-linux-x86_64-gpu/1.3.1-SNAPSHOT/ >> > > >> > > Please remember to TEST first before voting accordingly: >> > > +1 = approve >> > > +0 = no opinion >> > > -1 = disapprove (provide reason) >> > > >> > > >> > > Best regards, >> > > Anton >> > > >> > >> >
