Return-Path: 
 <issues-return-42733-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D16629D5F
	for <apmail-hbase-issues-archive@www.apache.org>;
 Fri,  6 Apr 2012 11:37:44 +0000 (UTC)
Received: (qmail 7360 invoked by uid 500); 6 Apr 2012 11:37:44 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 7322 invoked by uid 500); 6 Apr 2012 11:37:44 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 7308 invoked by uid 99); 6 Apr 2012 11:37:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2012 11:37:44 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2012 11:37:43 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 11D5735C312
	for <issues@hbase.apache.org>; Fri,  6 Apr 2012 11:37:23 +0000 (UTC)
Date: Fri, 6 Apr 2012 11:37:23 +0000 (UTC)
From: "nkeywal (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2144162784.22866.1333712243088.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <809822757.17862.1333645581561.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5729) Jenkins build failing; failsafe
 NPE'ing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

nkeywal commented on HBASE-5729:
--------------------------------

{noformat}
mvn -e  site install assembly:single  -Dtest.exclude.pattern="whatever"
{noformat}

works as well. It seems that surefire wants the variables to be defined in
{noformat}
            <excludes>
              <exlude>${unittest.include}</exlude>
              <exclude>**/*$*</exclude>
              <exclude>${test.exclude.pattern}</exclude>
            </excludes>
{noformat}

So suppressing the line in the .pom sould be ok, even if it does not explain why it was working before.

                
> Jenkins build failing; failsafe NPE'ing
> ---------------------------------------
>
>                 Key: HBASE-5729
>                 URL: https://issues.apache.org/jira/browse/HBASE-5729
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>
> Builds up on jenkins have been failing over the last few days.  Looking at it w/ nkeyway, its kinda odd.  I ran exact command locally as did N and it works fine.  I removed all of my repo and still works.  N looked at surefire source.  Its the includes that is coming back empty causing the NPE we see up on jenkins.  Extra odd is that it does not seem like it a checkin of ours that brought this on.  See here where its 'working' on 0.94 branch: https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.94/76/  Then a little later Ted triggers a build w/ no changes made: https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.94/77/console
> Its failing running the integration test phase.  Let me mess around and try and get it going again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira