[jira] [Updated] (HIVE-4420) HCatalog unit tests stop after a failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HIVE-4420: Fix Version/s: 0.11.0 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.11.0, 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
[jira] [Updated] (HIVE-4420) HCatalog unit tests stop after a failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HIVE-4420: Fix Version/s: (was: 0.12.0) 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.11.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
[jira] [Updated] (HIVE-4420) HCatalog unit tests stop after a failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated HIVE-4420: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks Sushanth. 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
[jira] [Updated] (HIVE-4420) HCatalog unit tests stop after a failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated HIVE-4420: - Attachment: HIVE-4420.patch Attaching a patch that puts the tests in a parallel structure so that each one is run. Tests are still run serially by setting parallelism to 1, but a side effect of parallel is that each of its components is run even if one of them fails. 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
[jira] [Updated] (HIVE-4420) HCatalog unit tests stop after a failure
[ https://issues.apache.org/jira/browse/HIVE-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated HIVE-4420: - Status: Patch Available (was: Open) 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
