Re: Apache MXNet build failures are mostly valid - verify before merge

point Joern, I'll follow up on that. Regards, Gautam On Fri, Sep 29, 2017 at 2:20 AM, Joern Kottmann <kottm...@gmail.com> wrote: > It also makes sense to block too old PRs from merging, because the > test results are outdated and the build might fail after it gets > merged. > >

Re: Apache MXNet build failures are mostly valid - verify before merge

Hi All, The master branch is protected now. Please review your PR for merge. Thanks to Infra team for following up on this. Regards, Gautam On Mon, Oct 2, 2017 at 1:19 PM, Gautam <gautamn...@gmail.com> wrote: > Thanks All. > > I've created the JIRA to mark the protected br

Re: Apache MXNet build failures are mostly valid - verify before merge

Hi Chris, I mean make "master branch protected" of MXNet. -Gautam On Wed, Sep 27, 2017 at 11:04 PM, Chris Olivier <cjolivie...@gmail.com> wrote: > What does this mean? "Mx-net branch protected"? > > On Wed, Sep 27, 2017 at 9:59 PM Tsuyoshi OZAWA <ozawa

Re: Apache MXNet build failures are mostly valid - verify before merge

te on it. My main motive was to "*Can't have changes merged into it until required status checks pass*" -Gautam On Wed, Sep 27, 2017 at 11:09 PM, Chris Olivier <cjolivie...@gmail.com> wrote: > What does that mean? "Protected"? Protected from what? > > On

Re: CI system seems to be using python3 for python2 builds

send the PR, if you have it ready. -Gautam On Wed, Sep 27, 2017 at 9:39 PM, Tsuyoshi Ozawa <oz...@apache.org> wrote: > Hi Kumar, > > Thanks for looking into the issue. How is the progress of this problem? > Shouldn't we call /usr/bin/env python2 or python2.7 in following > so

Re: 1.0 release problems and TVM

1,0 > >> release. > >> Can someone on tvm team please address this? > >> > >> Also, is mxnet 1.0 using tvm now? I don't recall this being discussed > at > >> all on dev@. If not, why is it in there? There's no licensing > references > >> as well, which is problematic. Is it necessary for 1.0? > >> > > > -- Best Regards, Gautam Kumar

Re: Protected master needs to be turned off

-1 Please see inline. On Nov 19, 2017 12:51 PM, "Eric Xie" wrote: Hi all, I'm starting this thread to vote on turning off protected master. The reasons are: 1. Since we turned on protected master pending PRs has grown from 40 to 80. It is severely slowing down development.

Re: [VOTE] Release MXNet version 0.12.0.rc0

om/apache/incubator-mxnet/tree/0.12.0.rc0>0 > > (Note: The README.md points to the 0.12.0 tag and does not work at the > moment.) > > > Please make sure you TEST before you vote accordingly: > > > +1 = approve > > > +0 = no opinion > > > -1 = disapprove (provide reason) > > > Thanks, > > Meghna Baijal > -- Best Regards, Gautam Kumar

Re: [VOTE] Release Apache MXNet(incubating) version 1.2.0.RC1

rt now (Thursday, April 26th) and end > at > > > 3:00 > > > > > PM > > > > > > PDT, Monday, April 30th. > > > > > > > > > > > > Link to release notes: > > > > > > https://cwiki.apache.org/confluence/display/MXNET/ > > > > > > Apache+MXNet+%28incubating%29+1.2.0+Release+Notes > > > > > > > > > > > > Link to release candidate 1.2.0.rc1: > > > > > > https://github.com/apache/incubator-mxnet/releases/tag/1.2.0.rc1 > > > > > > > > > > > > Voting results for 1.2.0.rc0: > > > > > > https://lists.apache.org/thread.html/ > > c79327b822c47ec4f97dad463fc6cd > > > > > > fe2aa517772d22eca24c5c300f@%3Cdev.mxnet.apache.org%3E > > > > > > > > > > > > View this page, click on “Build from Source”, and use the source > > code > > > > > > obtained from the 1.2.0.rc1 tag: > > > > > > https://mxnet.incubator.apache.org/install/index.html > > > > > > > > > > > > (Note: The README.md points to the 1.2.0 tag and does not work at > > the > > > > > > moment.) > > > > > > > > > > > > Please see a preview of the 1.2.0 version of the website at: > > > > > > http://mxnet.incubator.apache.org/versions/1.2.0/index.html > > > > > > > > > > > > > > > > > > Anirudh > > > > > > > > > > > > > > > > > > > > > -- Best Regards, Gautam Kumar

Re: Switch PR validation to PR-merge

+1 On Jan 10, 2018 1:25 AM, "Marco de Abreu" wrote: > Hello, > > TLDR: We wish to change how PRs are validated, turning off PR-head which > tests PRs in their current branch, and turning on PR-merge, which tests PRs > rebased on the current master branch. We

Re: CI system seems to be using python3 for python2 builds

Hi Kellen, This issue has been happening since last 3-4 days along with few other test failure. I am looking into it. -Gautam On 9/26/17, 7:45 AM, "Sunderland, Kellen" <kell...@amazon.de> wrote: I’ve been noticing in a few failed builds that the stack trace

Re: Apache MXNet build failures are mostly valid - verify before merge

at the cost of quality I will vote for the quality. We can work on improving the infrastructure to improve the overall speed. If you have any specific concerns on availability of Jenkins please point out. -Gautam On 9/28/17, 11:38 AM, "Chris Olivier" <cjolivie...@gma

Re: Apache MXNet build failures are mostly valid - verify before merge

that new slaves are not causing any infrastructure issue and capable to perform as good as existing slaves. -Gautam On 8/31/17, 5:27 PM, "Lupesko, Hagay" <lupe...@gmail.com> wrote: @madan looking into some failures – you’re right… there’s multiple issues going on, some of t