Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAAjhxrqGRgbWUkHY6h1cE1UbqJEsJYJNq71ZwQbDaVCghqQQEg@mail.gmail.com>
References: 
 <CALte62xDxReGn23W=8VFOLSqE1dD2R_Vhavo6CFqW4fEgR4nnw@mail.gmail.com>
 <CAAjhxrqGRgbWUkHY6h1cE1UbqJEsJYJNq71ZwQbDaVCghqQQEg@mail.gmail.com>
From: Sean Busbey <busbey@cloudera.com>
Date: Tue, 5 Jan 2016 12:53:59 -0600
Message-ID: 
 <CAGHyZ6LK2k6-0m-f0KbNjurYx=01gaHGWx39V12Xk0OrkZEmxA@mail.gmail.com>
Subject: Re: truncated checkstyle output
To: dev <dev@hbase.apache.org>
Cc: stack <stack@apache.org>
Content-Type: multipart/alternative; boundary=001a1141ef26d75aee05289ac38b

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

I'm hoping to have a first pass of transitioning to yetus up later this
week, so maybe this issue will be obviated?

On Tue, Jan 5, 2016 at 11:49 AM, Apekshit Sharma <appy@cloudera.com> wrote:

> Stack was facing same issue yesterday with
> https://builds.apache.org/job/PreCommit-HBASE-Build/17118. I think he
> tried
> re-running it. Don't know after that.
>
> On Tue, Jan 5, 2016 at 7:39 AM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > Hi,
> > I was looking at checkstyle warnings for one of my patches.
> > I noticed that both trunkCheckstyle.xml and patchCheckstyle.xml were
> > truncated, resulting in bad-formed xml files.
> >
> > I downloaded trunkCheckstyle.xml from another QA run (not for my patch)
> and
> > observed truncated xml:
> >
> >
> https://builds.apache.org/job/PreCommit-HBASE-Build/17120/artifact/patchprocess/
> >
> > Here was the tail of trunkCheckstyle.xml :
> >
> > <error line="82" severity="error" message="At-clause should have a
> > non-empty description."
> >
> >
> source="com.puppycrawl.tools.checkstyle.checks.javadoc.NonEmptyAtclauseDescriptionCheck"/>
> > </file>
> > <file
> >
> >
> name="/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase/hbase-client/src/main/java/org/apache/hadoop/hbase/security/access/Permission.java">
> > <error
> >
> > Has anyone else noticed similar issue ?
> >
> > Thanks
> >
>
>
>
> --
>
> Regards
>
> Apekshit Sharma | Software Engineer, Cloudera | Palo Alto, California |
> 650-963-6311
>


-- 
Sean

--001a1141ef26d75aee05289ac38b--