Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mxnet.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAC_CU1iC0Gxt+C1jy7=aW9kQN8bghpdSpNyzyQZmBi1qpVeuFg@mail.gmail.com>
References: <CAHb99Ty8maW2pR_bdDtirhg4LakJ=NfYwbQ=y84y3GCpFMmrTw@mail.gmail.com>
 <CAC2KA1p3wLdSBiyPZNwO4uUbqS_bj39qVAEX5_U1NeFeSqG=8A@mail.gmail.com>
 <CAHb99Tz8def3494K7i=TYF5Qk6j1gQRrr7oJ7k2LvokXhfiV7A@mail.gmail.com>
 <CABgAAfeyP=BBMQVBur9o-Zf9r3Uk8k3tOjjirzc2KUi0hi1L9A@mail.gmail.com>
 <CAHb99Tz77CSk4fd=ec=S9DRJDZpnnSTcnePwqCw_1iiBjM8vGA@mail.gmail.com>
 <CABgAAffNcJ9uLp1g8a0NRzUkUPXqP7p=PJL0Y6ZREbGtjP5yyQ@mail.gmail.com>
 <CAC_CU1geDBg2bTxEHUQVK-M4YzJvNGnjdfdN+5gdKfTKwVGLHw@mail.gmail.com> <CAC_CU1iC0Gxt+C1jy7=aW9kQN8bghpdSpNyzyQZmBi1qpVeuFg@mail.gmail.com>
From: Marco de Abreu <marco.g.abreu@googlemail.com>
Date: Fri, 8 Dec 2017 12:20:58 +0100
Message-ID: <CAHTWJDPo6-yrCsTf-d6_MENKyGL2vo17Weq=xMDwoAFyyWcO0w@mail.gmail.com>
Subject: Re: [VOTE] Disable Appveyor
To: dev@mxnet.incubator.apache.org
Content-Type: multipart/alternative; boundary="f403045e9ac462a01c055fd263a3"
archived-at: Fri, 08 Dec 2017 11:21:45 -0000

--f403045e9ac462a01c055fd263a3
Content-Type: text/plain; charset="UTF-8"

Who's going to maintain and fix problems which will arise with travis CI?
Due to the protected master branch, this can cause some serious blocking
issues. I think it should be tested and everything fixed before we
re-enable travis CI.

My proposal is to wait for stage 3 (new features) of the new CI launch
until we start working on Travis CI.

On Fri, Dec 8, 2017 at 12:07 PM, Pedro Larroy <pedro.larroy.lists@gmail.com>
wrote:

> Can somebody re-enable travis CI so we can do mac builds?  currently
> the unit tests don't build in Mac because Mac is not tested.
>
> On Fri, Dec 8, 2017 at 12:02 PM, Pedro Larroy
> <pedro.larroy.lists@gmail.com> wrote:
> > +1
> >
> >
> >
> > On Fri, Dec 8, 2017 at 1:02 AM, Chris Olivier <cjolivier01@gmail.com>
> wrote:
> >> +1
> >>
> >> On Thu, Dec 7, 2017 at 3:57 PM, kellen sunderland <
> >> kellen.sunderland@gmail.com> wrote:
> >>
> >>> It's using a fixed binary version of openblas and opencv, so the
> versions
> >>> there might be different than what we use.  It's compiling with
> profiler
> >>> enabled.  A few build flags.  However all it's doing is building, it
> >>> doesn't test.
> >>>
> >>> The best lines to compare would be this:
> >>> https://github.com/apache/incubator-mxnet/blob/master/Jenkinsfile#L236
> >>> to this:
> >>> https://ci.appveyor.com/project/ApacheSoftwareFoundation/
> >>> incubator-mxnet/build/1.0.4047#L96
> >>> to get an idea of the (minor) differences.
> >>>
> >>>
> >>> On Dec 8, 2017 12:51 AM, "Chris Olivier" <cjolivier01@gmail.com>
> wrote:
> >>>
> >>> Does Appveyor do anything that Jenkins isn't doing? Anything at all?
> >>>
> >>> On Thu, Dec 7, 2017 at 3:41 PM, kellen sunderland <
> >>> kellen.sunderland@gmail.com> wrote:
> >>>
> >>> > @Chris nope, AppVeyor has only ever supported Windows.
> >>> >
> >>> > I think some people are thinking of Travis CI, which is a pretty
> great
> >>> > managed CI that does support MacOS/Linux. I'd be in favour of
> setting up
> >>> a
> >>> > Mac build there.  At a minimum we can at least start a new compiling
> task
> >>> > with clang in the new CI.
> >>> >
> >>> > On Dec 7, 2017 11:41 PM, "Indhu" <indhubharathi@gmail.com> wrote:
> >>> >
> >>> > > +1
> >>> > >
> >>> > > My build is waiting in queue for 13 hours now.
> >>> > >
> >>> > >
> >>> > > On Thu, Dec 7, 2017, 11:26 AM kellen sunderland <
> >>> > > kellen.sunderland@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > Background:  Appveyor is a free-to-use (for opensource) CI system
> >>> that
> >>> > > > specializes in providing support for Windows environments.
> Appveyor
> >>> is
> >>> > > > currently running a very simple windows build for MXNet.
> >>> Specifically
> >>> > we
> >>> > > > are generating build files via cmake, and then building with
> Visual
> >>> > > Studio
> >>> > > > 14 with fairly standard build options.
> >>> > > >
> >>> > > > Problem: AppVeyor frequently slows down our release process and
> has
> >>> > been
> >>> > > > made redundant by the new CI system's windows builds.
> >>> > > >
> >>> > > > Action: Let's remove AppVeyor and rely on the new CI's windows
> build
> >>> > > > systems which has very similar functionality.
> >>> > > >
> >>> > > > Vote will close Monday Dec 11th and will rely on lazy consensus.
> >>> > > >
> >>> > > > -Kellen
> >>> > > >
> >>> > >
> >>> >
> >>>
>

--f403045e9ac462a01c055fd263a3--