Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Fri, 3 Jan 2014 04:04:52 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12687039.1388697439266.36048.1388721892574@arcas>
In-Reply-To: <JIRA.12687039.1388697439266@arcas>
References: <JIRA.12687039.1388697439266@arcas>
Subject: [jira] [Resolved] (HADOOP-10200) Fix precommit script
 patch_tested.txt fallback option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved HADOOP-10200.
----------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

> Fix precommit script patch_tested.txt fallback option
> -----------------------------------------------------
>
>                 Key: HADOOP-10200
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10200
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>         Attachments: HADOOP-10200.patch
>
>
> HADOOP-10199 created a "fallback" option when there is successful artifact. However that fallback option used the jenkins lastBuild build indicator. It appears that does not mean the last completed build, but strictly the last build, which in this context is the current build. The current build is running so it doesn't have any artifacts.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)