[jira] [Created] (HADOOP-9765) Precommit Admin job chokes on issues without an attachement

["Brock Noland (JIRA)" <ji...@apache.org>]

Brock Noland created HADOOP-9765:
------------------------------------

             Summary: Precommit Admin job chokes on issues without an attachement
                 Key: HADOOP-9765
                 URL: https://issues.apache.org/jira/browse/HADOOP-9765
             Project: Hadoop Common
          Issue Type: Bug
          Components: build
            Reporter: Brock Noland
            Assignee: Brock Noland


Check out this file:  https://builds.apache.org/job/PreCommit-Admin/lastSuccessfulBuild/artifact/patch_tested.txt

It has "corrupt" data:
{noformat}
HIVE-4877HDFS-5010,12593214
HIVE-4877HBASE-8693,12593082
HIVE-4877YARN-919,12593107
YARN-905,12593225
HIVE-4877HBASE-8752,12588069
{noformat}

which resulted in the Hive precommit job being called with the ISSUE_NUM of 5010, 8693, 919, and 8752.

Looking at the script and some output, I pulled from the last run, it looks like it gets hosed up when there is a JIRA which is PA but doesn't have an attachment (as ZK-1402 is currently sitting). For example:

This is the bad data the script is encountering:
{noformat}
$ grep -A 2 'ZOOKEEPER-1402' patch_available2.elements 
ZOOKEEPER-1402
HBASE-8348
 id="12592318"
{noformat}

This is where it screws up:

{noformat}
$ awk '{ printf "%s", $0 }' patch_available2.elements | sed -e "s/\W*id=\"/,/g" | perl -pe "s/\"/\n/g"  | grep ZOOKEEPER-1402
ZOOKEEPER-1402HBASE-8348 ,12592318
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira