Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 24 Aug 2015 19:59:46 +0000 (UTC)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12858388.1440446373000.150338.1440446386672@Atlassian.JIRA>
In-Reply-To: <JIRA.12858388.1440446373000@Atlassian.JIRA>
References: <JIRA.12858388.1440446373000@Atlassian.JIRA>
 <JIRA.12858388.1440446373473@arcas>
Subject: [jira] [Created] (HADOOP-12351) Can't run test-patch with
 start-build-env.sh
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jakob Homan created HADOOP-12351:
------------------------------------

             Summary: Can't run test-patch with start-build-env.sh
                 Key: HADOOP-12351
                 URL: https://issues.apache.org/jira/browse/HADOOP-12351
             Project: Hadoop Common
          Issue Type: Bug
          Components: test, yetus
            Reporter: Jakob Homan
            Priority: Minor


The Docker instance started by start-build-env.sh drops the user into a root directory wherein other directories (say ~/download) are not accessible, so one cannot pull patches to test into it.  The dev-support/test-patch.sh script requires a clean environment with no extra files, such as the patch to test.  Between these two restrictions, one can't use the docker env to run test-patch.  We should either -v a volume where patches can be stashed, or allow test-patch.sh to ignore patch files' existences.


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