Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 24 Sep 2015 22:33:04 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12862300.1441683811000.67460.1443133984922@Atlassian.JIRA>
In-Reply-To: <JIRA.12862300.1441683811000@Atlassian.JIRA>
References: <JIRA.12862300.1441683811000@Atlassian.JIRA>
 <JIRA.12862300.1441683811121@arcas>
Subject: [jira] [Commented] (HBASE-14378) Get TestAccessController* passing
 again on branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907162#comment-14907162 ] 

Hadoop QA commented on HBASE-14378:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12762239/14378.branch-1.v7.txt
  against branch-1 branch at commit 9557bc7dfa3a48b668dda379a25eeaba41d33356.
  ATTACHMENT ID: 12762239

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 27 new or modified tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15728//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15728//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15728//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15728//console

This message is automatically generated.

> Get TestAccessController* passing again on branch-1
> ---------------------------------------------------
>
>                 Key: HBASE-14378
>                 URL: https://issues.apache.org/jira/browse/HBASE-14378
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: 14378.branch-1.txt, 14378.branch-1.v2.txt, 14378.branch-1.v2.txt, 14378.branch-1.v2.txt, 14378.branch-1.v6.txt, 14378.branch-1.v7.txt, 14386.branch-1.v3 (1).txt, 14386.branch-1.v3.txt, 14386.branch-1.v3.txt, 14386.branch-1.v4.do.nothing.txt, 14386.branch-1.v5.txt
>
>
> TestAccessController* are failing reliably on branch-1. They go zombie. I learned that setting the junit test timeout facility on the class doesn't make the zombie timeout nor does setting a timeout on each test turn zombies to test failures; the test goes zombie on the way out in the tear down of the cluster.
> Digging, we are out of handlers... all are occupied.
> 3dacee6 HBASE-14290 Spin up less threads in tests cut the default thread count to 3 from 10. Putting the value back on these tests seems to make them pass reliably when I run locally.  For good measure, I'll add in the timeouts .


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)