[
https://issues.apache.org/jira/browse/SQOOP-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997632#comment-14997632
]
Hudson commented on SQOOP-2659:
-------------------------------
SUCCESS: Integrated in Sqoop2 #942 (See
[https://builds.apache.org/job/Sqoop2/942/])
SQOOP-2659. Sqoop2: Do not stop services that haven't been started in
(hshreedharan:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=4459bd925103793663631d75e613e5e32c631cce])
* common-test/src/main/java/org/apache/sqoop/common/test/kafka/TestUtil.java
* test/src/main/java/org/apache/sqoop/test/testcases/HiveConnectorTestCase.java
> Sqoop2: Do not stop services that haven't been started in our integration
> test suite
> ------------------------------------------------------------------------------------
>
> Key: SQOOP-2659
> URL: https://issues.apache.org/jira/browse/SQOOP-2659
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2659.patch, SQOOP-2659.patch
>
>
> While investigating pre-commit hook failures on SQOOP-2652 I was side
> tracked at a lot by seeing various exceptions from Hive and Kafka test cases
> with {{NullPointerException}} and spending time investigating them.
> Upon further investigation I've noticed that the whole reason is that we're
> shutting down something that wasn't started and hence the NPE. The problem
> was that my newly added test case had added an {{assume}} statement in
> {{@Before*}} family of methods. The {{assume}} statement return false and
> stopped test execution before the Hive/Kite test cases got initialized.
> However the testng will execute all tear down methods ({{@After*}} and not
> only those that have been initialized. Hence the tear down methods must be
> smart enough to not die if the initialization in fact did not happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
