oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Barber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-644) Protocol tests are extremely buggy and unstable
Date Fri, 05 Sep 2014 21:56:29 GMT

    [ https://issues.apache.org/jira/browse/OODT-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123665#comment-14123665

Tom Barber commented on OODT-644:

pushed some stuff for this to make the tests a) not fail b) more mockable

> Protocol tests are extremely buggy and unstable
> -----------------------------------------------
>                 Key: OODT-644
>                 URL: https://issues.apache.org/jira/browse/OODT-644
>             Project: OODT
>          Issue Type: Bug
>          Components: push pull framework
>    Affects Versions: 0.6
>            Reporter: Chris A. Mattmann
>            Assignee: Tom Barber
>            Priority: Critical
>             Fix For: 0.8
> The tests in:
> * protocol-sftp
> * protocol-ftp 
> Are pretty buggy and unstable. For example, the protocol-ftp starts up a server on port
9000 (the default file manager port -- which if you have a file manager running, this will
not pass, and it will hang and then I was only able to make it release the port by restarting
my computer even though lsof and netstat didn't show anything). As another example, the protocol-sftp
plugin starts up an SSH server on the seemingly default port of 12222 (since it's not provided
a specific port value -- though it seems to also start it up on 22?). These port conflicts
would easily be eliminated by Mock objects, and I think they should be since we don't need
to be grabbing ports for unit tests.

This message was sent by Atlassian JIRA

View raw message