Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALwhT94w=be83FrdfKV9zYMFX0ms6NROF1Mjmg1x6bH3fBYnpA@mail.gmail.com>
References: <A636A821-9A26-4607-8861-BEB811D0A938@altiscale.com>
	<CALwhT94w=be83FrdfKV9zYMFX0ms6NROF1Mjmg1x6bH3fBYnpA@mail.gmail.com>
Date: Thu, 29 Oct 2015 07:53:16 +0530
Message-ID: 
 <CADoWKTDZP4mr=-EBEwc1pk25o4JTKxKoiQczoTP4vG13jBvruw@mail.gmail.com>
Subject: Re: FYI: Major, long-standing Issue with trunk's test-patch
From: Vinayakumar B <vinayakumarb@apache.org>
To: common-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a11c3f1f4598b01052334fe60

--001a11c3f1f4598b01052334fe60
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

  So I=E2=80=99m going to turn on Yetus for *ALL* Hadoop precommit jobs
> later tonight. (Given how backed up Jenkins is at the moment, there is
> plenty of time. haha) Anyway, if you see =E2=80=9CPowered by Yetus=E2=80=
=9D in the Hadoop
> QA posts, you=E2=80=99ve got Yetus.  If you don=E2=80=99t see it, it ran =
on trunk=E2=80=99s
> test-patch.

+1,

Report looks very clean, and multiple JDK runs helps as well. Also parallel
run is enabled for HDFS precommit as well.

One issue, Looks like ASF licence check is done on files in build directory
also, which generates too many errors. Just need to skip this directory.

Regards,
Vinay

On Thu, Oct 29, 2015 at 4:11 AM, Karthik Kambatla <kasha@cloudera.com>
wrote:

> On Tue, Oct 27, 2015 at 7:44 PM, Allen Wittenauer <aw@altiscale.com>
> wrote:
>
> >
> >         Today I discovered that an old, old code change (circa 2012)
> > caused certain maven modules to be skipped during the precommit testing=
.
> > That code had been carried forward through all the rewrites, bug fixes,
> > etc, over the years likely because it seemed the correct thing to do. I=
t
> is
> > clearly not, since at least hadoop-pipes was getting ignored.  I have n=
ot
> > evaluated the impact of the bug on other parts of the Hadoop code base.
> >
>
> Pointer to this bug?
>
>
> >
> >         I=E2=80=99ve got sitting in the Hadoop beta test branch of Yetu=
s what I
> > think is a potential fix to that bug.  Initial testing shows all system=
s
> > are go.
> >
> >         Additionally:
> >
> >         * After several weeks, Yetus being used for Hadoop Common has
> been
> > more or as stable as trunk=E2=80=99s, but testing significantly more pa=
rts.
> >         * People are still reporting bugs on trunk=E2=80=99s test-patch=
 that have
> > been fixed for months in Yetus.
> >         * People are still confused as to which version is running wher=
e,
> > despite the email thread just a few days ago.  (*exasperated sigh here*=
)
> >
> >         So I=E2=80=99m going to turn on Yetus for *ALL* Hadoop precommi=
t jobs
> > later tonight. (Given how backed up Jenkins is at the moment, there is
> > plenty of time. haha) Anyway, if you see =E2=80=9CPowered by Yetus=E2=
=80=9D in the Hadoop
> > QA posts, you=E2=80=99ve got Yetus.  If you don=E2=80=99t see it, it ra=
n on trunk=E2=80=99s
> > test-patch.
> >
>
> +1
>
>
> >
> >         (=E2=80=A6 and now begin the threads on everyone freaking out a=
nd/or not
> > reading the above =E2=80=A6)
>

--001a11c3f1f4598b01052334fe60--