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

Sqoop QA bot commented on SQOOP-2202:
-------------------------------------

Testing file 
[SQOOP-2202.patch|https://issues.apache.org/jira/secure/attachment/12704801/SQOOP-2202.patch]
 against branch sqoop2 took 0:33:02.501459.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} Some of slow integration tests failed 
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1159/artifact/patch-process/test_integration_slow.txt],
 executed 0 tests)
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All fast unit tests passed (executed 261 tests)
{color:green}SUCCESS:{color} All slow unit tests passed (executed 1 tests)
{color:green}SUCCESS:{color} All fast integration tests passed (executed 15 
tests)

Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1159/console].

This message is automatically generated.

> Sqoop2: Add validator to check existence of local directory on Sqoop 2 server
> -----------------------------------------------------------------------------
>
>                 Key: SQOOP-2202
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2202
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2202.patch, SQOOP-2202.patch
>
>
> It would be useful to have general validator for ensuring existence of 
> certain directory on Sqoop 2 server machine - for example to load up external 
> configuration files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to