sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3350) Fix tests which use warehouse-dir as target-dir
Date Fri, 27 Jul 2018 09:52:00 GMT

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

Hudson commented on SQOOP-3350:
-------------------------------

SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1191 (See [https://builds.apache.org/job/Sqoop-hadoop200/1191/])
SQOOP-3350: Fix tests which use warehouse-dir as target-dir (bogi: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=1213b7725a65e561d8db071141e04944c85d1f94])
* (edit) src/test/org/apache/sqoop/manager/mysql/MySqlColumnEscapeImportTest.java
* (edit) src/test/org/apache/sqoop/TestFreeFormQueryImport.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleColumnEscapeImportTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleSplitterTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleIncrementalImportTest.java
* (edit) src/test/org/apache/sqoop/manager/oracle/OracleSpecialCharacterTableImportTest.java


> Fix tests which use warehouse-dir as target-dir
> -----------------------------------------------
>
>                 Key: SQOOP-3350
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3350
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.7
>            Reporter: Szabolcs Vasas
>            Assignee: Szabolcs Vasas
>            Priority: Major
>         Attachments: SQOOP-3350.patch
>
>
> Some Sqoop tests use the value of theĀ org.apache.sqoop.testutil.BaseSqoopTestCase#getWarehouseDir
as target-dir:
> {code:java}
> args.add("--target-dir");
> args.add(getWarehouseDir());
> {code}
> This leads to an error when the warehouse directory exists which can happen if a previous
test does not clean up properly.
> The issue was found when executing the tests with Gradle since it probably executes the
tests in a different order.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message