Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPgpW0YmYm5vKcpq99JNd0mVTu8_f-Ta4oOgTfSpnydCJxLvwA@mail.gmail.com>
References: 
 <CAPJXddaGt7ugLpRK1wSy4AgtzXjPHGaHsMiZmq47a-=t2KJBaw@mail.gmail.com>
	<CAOjayEfSoG+P8VqmGVnx5yuBzgpnURS4uFz0vsnO01u-aucVGg@mail.gmail.com>
	<CAPgpW0YaqGhGMJvLcMhDLSgap9dAnsQqvPvBcmzXi+dxNC1YgQ@mail.gmail.com>
	<CAOjayEcw6XOXoWcvb-gciBY+Uh2acYiW+yT5Ao0MmAtTyrp5pw@mail.gmail.com>
	<CAPJXddZ9ZUmwS3M5AOms8hmRy22JurePiTNQmnsbEuFAjRq6FQ@mail.gmail.com>
	<CAG+aQFkOw_CHY3f2j00MhkE5Y_kzcZYiPJc9EvoUwPJaiNmZMg@mail.gmail.com>
	<CAPJXddbWKLrRSXjnquuuNeDBLzz7-WigjvM-gFDO484YTQ6_tQ@mail.gmail.com>
	<CAPgpW0YmYm5vKcpq99JNd0mVTu8_f-Ta4oOgTfSpnydCJxLvwA@mail.gmail.com>
Date: Mon, 1 Feb 2016 10:37:52 -0800
Message-ID: 
 <CAPJXddZUKCGMR53FVw3pw7ciBbGHzQ1QdxNPjc9HRESmTnGUQQ@mail.gmail.com>
Subject: Re: install check good results
From: Ivan Novick <inovick@pivotal.io>
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113cc584b99ac5052ab9ae66

--001a113cc584b99ac5052ab9ae66
Content-Type: text/plain; charset=UTF-8

Cool, Thx Goden!

On Mon, Feb 1, 2016 at 10:34 AM, Ting(Goden) Yao <tyao@pivotal.io> wrote:

> We only have 2 admins at the moment. Radar and Roman.
> Radar has assigned this JIRA to himself, so let's get his input on that.
> I'll modify the JIRA to include installcheckgood as acceptance criteria.
>
> On Mon, Feb 1, 2016 at 10:33 AM Ivan Novick <inovick@pivotal.io> wrote:
>
> > Hmmm, so who has access to that infrastructure?
> >
> > We should be running the basic installcheck-good at a minimum on the
> latest
> > checkins IMO
> >
> > Cheers,
> > Ivan
> >
> > On Mon, Feb 1, 2016 at 10:29 AM, Noa Horn <nhorn@pivotal.io> wrote:
> >
> > > Just to clarify, the jenkins build only compiles HAWQ. It doesn't run
> any
> > > tests (unit tests or installcheck-good) at the moment.
> > >
> > > On Mon, Feb 1, 2016 at 10:21 AM, Ivan Novick <inovick@pivotal.io>
> wrote:
> > >
> > > > What is required to fix it?
> > > >
> > > > Is the Jenkins config need fixing?
> > > >
> > > > We need to see the output of the build and the tests.
> > > >
> > > > Cheers,
> > > > Ivan
> > > >
> > > > On Mon, Feb 1, 2016 at 10:17 AM, Caleb Welton <cwelton@pivotal.io>
> > > wrote:
> > > >
> > > > > Filing a jira is a good start.  This seems like an important
> > priority.
> > > > > Anyone want to volunteer to get this resolved?
> > > > >
> > > > > On Mon, Feb 1, 2016 at 10:10 AM, Ting(Goden) Yao <tyao@pivotal.io>
> > > > wrote:
> > > > >
> > > > > > I have filed this JIRA to fix the issue:
> > > > > > https://issues.apache.org/jira/browse/HAWQ-331
> > > > > > still open right now.
> > > > > > -Goden
> > > > > >
> > > > > > On Mon, Feb 1, 2016 at 9:57 AM Caleb Welton <cwelton@pivotal.io>
> > > > wrote:
> > > > > >
> > > > > > > We have integration with the Apache Jenkins instance for every
> > pull
> > > > > > > request[1].  However if you go into the console output of those
> > > > Jenkins
> > > > > > > builds you can see that:
> > > > > > > a) Every change for a while has been failing to complete the
> > build.
> > > > > > > b) Everything is still reporting green.
> > > > > > >
> > > > > > > [1] <https://builds.apache.org/job/HAWQ-build-pullrequest/>
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Jan 31, 2016 at 8:17 PM, Ivan Novick <
> inovick@pivotal.io
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Do we have output of install check good (red/green) tests
> > showing
> > > > on
> > > > > a
> > > > > > CI
> > > > > > > > somewhere for open source Hawq based on the latest code
> > checkins
> > > to
> > > > > > > MASTER?
> > > > > > > >
> > > > > > > > Do we have a way to confirm the latest code on MASTER is
> green?
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Ivan
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--001a113cc584b99ac5052ab9ae66--