You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sushanth Sowmyan (JIRA)" <ji...@apache.org> on 2013/04/26 23:52:16 UTC
[jira] [Commented] (HIVE-4420) HCatalog unit tests stop after a
failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643275#comment-13643275 ]
Sushanth Sowmyan commented on HIVE-4420:
----------------------------------------
Looks good to me, I've faked a test failure and am running tests. If tests continue to run, I will go ahead and commit.
One important note to people visiting this bug later - the patch provided is for hcatalog/build.xml, not the root build.xml.
> HCatalog unit tests stop after a failure
> ----------------------------------------
>
> Key: HIVE-4420
> URL: https://issues.apache.org/jira/browse/HIVE-4420
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure, HCatalog
> Affects Versions: 0.11.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Fix For: 0.12.0
>
> Attachments: HIVE-4420.patch
>
>
> HCatalog splits it's different components (core, hcatalog-pig-adaptor, webhcat, etc.) into separate build.xml files, all controlled by the top build.xml. A side effect of this is that when the user does "ant test" and the top build file is iterating through the tests, if one of the component's test targets fail then unit tests are not run for subsequent components. This means a failure in one component can mask issues in others.
> test should run on all the components even when there is a failure in one of the components.
--
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