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

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

Testing file 
[SQOOP-2405.patch|https://issues.apache.org/jira/secure/attachment/12742023/SQOOP-2405.patch]
 against branch sqoop2 took 0:40:34.227538.

{color:green}Overall:{color} +1 all checks pass

{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 682 tests)
{color:green}SUCCESS:{color} All slow unit tests passed (executed 1 tests)
{color:green}SUCCESS:{color} All fast integration tests passed (executed 28 
tests)
{color:green}SUCCESS:{color} All slow integration tests passed (executed 42 
tests)

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

This message is automatically generated.

> Sqoop2: Remove active wait in test cases after executeJob() call
> ----------------------------------------------------------------
>
>                 Key: SQOOP-2405
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2405
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-test
>            Reporter: Banmeet Singh
>            Assignee: Banmeet Singh
>            Priority: Minor
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2405.patch
>
>
> Some of the integration test cases actively wait polling the job submission 
> status after submitting the job using executeJob() with the assumption that 
> the Sqoop client job submission API does not block. This active wait can be 
> removed now that the Sqoop client executeJob() API is a blocking call.



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

Reply via email to