Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 51797100F6 for ; Tue, 30 Dec 2014 22:54:13 +0000 (UTC) Received: (qmail 70605 invoked by uid 500); 30 Dec 2014 22:54:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 70559 invoked by uid 500); 30 Dec 2014 22:54:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 70544 invoked by uid 99); 30 Dec 2014 22:54:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Dec 2014 22:54:13 +0000 Date: Tue, 30 Dec 2014 22:54:13 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3456) Accumulo client configuration affects unit tests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261602#comment-14261602 ] Christopher Tubbs commented on ACCUMULO-3456: --------------------------------------------- Which specific tests are affected? In my view, it seems odd that a unit test (unless it's a very specific one, testing the ZKInstance) should be affected, since unit tests should be written to be more narrow in their scope. It makes sense that integration tests would be affected, though. There are three solutions, I can think of: # Add a test resource for the client configuration, and use that first in the configuration search path. # Fix tests to only use Instance / Connector options which accept the configuration directly and bypass the search path. # Add a system property, {{-Daccumulo.config=}}, to use explicitly which will bypass the search path, and set that in our surefire configuration. I like option #3, generally, even beyond this issue, because it makes it easier to create service launch scripts. > Accumulo client configuration affects unit tests > ------------------------------------------------ > > Key: ACCUMULO-3456 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3456 > Project: Accumulo > Issue Type: Bug > Components: test > Reporter: Josh Elser > Fix For: 1.6.2, 1.7.0 > > > Accumulo unit tests (and probably integration tests, too) will fail if a client configuration file exists in the default location on the local filesystem {{~/.accumulo/config}}. > Our tests shouldn't be affected by the presence of these files on the local filesystem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)