Return-Path: 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 E0E3217331 for ; Mon, 27 Oct 2014 05:47:33 +0000 (UTC) Received: (qmail 49927 invoked by uid 500); 27 Oct 2014 05:47:33 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 49872 invoked by uid 500); 27 Oct 2014 05:47:33 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 49859 invoked by uid 99); 27 Oct 2014 05:47:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Oct 2014 05:47:33 +0000 Date: Mon, 27 Oct 2014 05:47:33 +0000 (UTC) From: "Misty Stanley-Jones (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-12347) Fix the edge case where Hadoop QA's parsing of attached patches breaks the JIRA status checker in dev-support/rebase_all_git_branches.sh 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/HBASE-12347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12347: ---------------------------------------- Attachment: HBASE-12347.patch Ready for review. To test, make a branch called HBASE-12207 and see if it gets picked up by the script as resolved. That JIRA ID is the only one that seems to be affected by this (though it would be easy to make a fake case). > Fix the edge case where Hadoop QA's parsing of attached patches breaks the JIRA status checker in dev-support/rebase_all_git_branches.sh > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-12347 > URL: https://issues.apache.org/jira/browse/HBASE-12347 > Project: HBase > Issue Type: Bug > Components: scripts > Reporter: Misty Stanley-Jones > Assignee: Misty Stanley-Jones > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-12347.patch > > > The rebase_all_hbase_branches.sh script is unable to detect that HBASE-12207 is closed, because for that one JIRA, the curl command that detects the status is returning the status, but also the text from Hadoop QA for each patch it has evaluated on the JIRA: > {code} > $ curl -s https://issues.apache.org/jira/browse/HBASE-12207 | grep resolution-val > > + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1)
> + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1) > + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1)
> + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1) > + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1)
> + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1) > + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1)
> + jira_status=$(curl -s $jira_url/$jira|grep resolution-val|sed -e "s/.*class=\"value\ //"|cut -d'"' -f 1) > {code} > All but the top line of output are from parsing comments from Hadoop QA. I think this is an edge case that will only to patches against that section of dev-support/rebase_all_git_branches.sh. However, I'm not sure the cleanest way to fix it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)