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

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

Testing file 
[SQOOP-1844.patch|https://issues.apache.org/jira/secure/attachment/12685121/SQOOP-1844.patch]
 against branch sqoop2 took 0:20:41.426583.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} Some unit tests failed
{color:red}ERROR:{color} Failed unit test: 
{{org.apache.sqoop.connector.idf.TestCSVIntermediateDataFormat}}
{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} Patch compiled
{color:green}SUCCESS:{color} All integration tests passed

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

This message is automatically generated.

> Sqoop2: Start Derby server in DerbyProvider on random port
> ----------------------------------------------------------
>
>                 Key: SQOOP-1844
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1844
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.4
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1844.patch
>
>
> We're currently starting Derby's server for test purpose on one specific port 
> - 1527. I found it particularly troublesome in SQOOP-1840 and SQOOP-1816 
> where the given port has been used and Derby had troubles to report startup 
> problems. However the issue is more generic - binding to single port means 
> that one can't possibly run two tests at the same time as they would be 
> stepping over each other. Hence I would like to propose to add a test utility 
> that will return a "random" available port on the machine and configure 
> {{DerbyProvider}} to use that. I'm assuming that such utility will be handy 
> even for future tests.



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

Reply via email to