Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 29 Aug 2012 21:07:07 +1100 (NCT)
From: "Carl Steinbach (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <87382775.11146.1346234827861.JavaMail.jiratomcat@arcas>
In-Reply-To: <1838883610.34771.1338829763435.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HIVE-3084) Hive CI failing due to
 script_broken_pipe1.q
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443941#comment-13443941 ] 

Carl Steinbach commented on HIVE-3084:
--------------------------------------

I think it would nice to continue running this test and simply ignore the cases where it fails. It looks like this can be accomplished with JUnit's @Ignore annotation: http://kentbeck.github.com/junit/javadoc/latest/org/junit/Ignore.html


> Hive CI failing due to script_broken_pipe1.q
> --------------------------------------------
>
>                 Key: HIVE-3084
>                 URL: https://issues.apache.org/jira/browse/HIVE-3084
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HIVE-3084_disable_failing_test.1.patch
>
>
> Hive's [CI job|https://builds.apache.org/job/Hive-trunk-h0.21/] regularly fails due to this test:
> {code}
> org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
> {code}
> Running just that test in a loop I'm not able to reproduce the issue locally. This may be related to state from a previous test causing this one to fail?
> {code}
> ant clean package
> for x in $(seq 1 10); 
>   do ant test -Dtestcase=TestNegativeCliDriver -Dqfile=script_broken_pipe1.q;
> done
> {code}

--
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